Confirm Cancellation

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

The description adds value beyond annotations by disclosing the output ('browser handoff') and the incomplete semantics, which warns the agent about unexpected behavior. Annotations already indicate destructiveHint=true, so no contradiction.

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?

Two concise sentences, front-loaded with the primary purpose. No wasted words.

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 does not indicate what the 'browser handoff' entails (e.g., a redirect URL) nor prerequisites like a valid cancellation draft. Given no output schema and a destructive action, more guidance is needed for safe usage.

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?

With 0% schema description coverage, the description fails to explain the 'draftId' parameter, its purpose, or how to obtain it. The single parameter is left entirely undocumented, forcing the agent to infer from the parameter name and pattern.

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 'Confirm a cancellation draft,' specifying the action (confirm) and resource (cancellation draft). It distinguishes from siblings like 'prepare_cancellation' and 'confirm_booking'.

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?

The description provides context about the tool's limitation ('returns a browser handoff' and 'semantics not verified'), but does not explicitly state when to use this tool vs alternatives or give usage guidelines like prerequisites.

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