Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already mark this as destructive and idempotent, and the description adds useful context: it requires the same agentApiKey and only applies pre-funding. It does not enumerate side effects, but the core cancellation behavior is clear and consistent with the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, tight sentence that conveys the action, scope, timing, and authentication requirement without filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter cancellation tool, the description covers purpose, timing, and auth reasonably well. However, the lack of any parameter descriptions—especially the optional reason field—and the absence of output expectations leaves some room for ambiguity about edge cases such as already-funded offers.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It only clarifies agentApiKey ('same agentApiKey') and leaves offerId and reason entirely implicit. The purpose hint that it must be 'an offer you submitted' indirectly maps to offerId, but reason is not explained at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action—withdrawing an offer—and clarifies the precise scope ('an offer you submitted') and timing ('before it is funded'). This clearly distinguishes cancel_offer from sibling tools like submit_offer and check_offer_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete conditions for use: only before funding and only with the same agentApiKey. It does not explicitly contrast with alternatives like submit_offer, but the timing condition strongly implies when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.