firestarter_cancel_drop

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

Annotations already include destructiveHint=true and idempotentHint=true. The description adds critical context: once cancelled, the drop stops being visible to the seller and can never be approved, and the request must be recreated. This goes beyond annotations by explaining consequences and scope of cancellation.

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?

Three sentences, each earning its place: main action, consequence, and constraint. Front-loaded with the verb 'Withdraw' and resource, providing a model context window efficient and easily scannable.

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?

The description fully covers the tool's purpose, conditions, consequences, and parameter sources. Given no output schema and two simple parameters, it is complete for an agent to select and invoke correctly, especially with sibling tools listed for differentiation.

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 already covers both parameters with descriptions (drop_id, program_id) at 100% coverage. The description adds value by specifying where to obtain each ID: 'from firestarter_create_drop's response' and 'from firestarter_my_markets', which helps the agent source correct parameter values.

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 clearly states the action: 'Withdraw a drop request you created', with specific conditions (on a market you own, pending seller's approval). It distinguishes from sibling tools like firestarter_approve_drop and firestarter_reject_drop by focusing on cancellation of a pending drop before decision.

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?

Provides explicit when-to-use: only for still-pending requests, and lists exclusions (live, expired, exhausted, already decided). Also names the alternative: create a new request with firestarter_create_drop if you change your mind, giving clear guidance on next steps.

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