Prepare Cancellation

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

The description adds value beyond annotations by stating that the cancellation draft is 'short-lived' and that confirmed cancellation requires browser handoff. Annotations already indicate non-readonly and non-destructive behavior, and the description aligns with those. Some behaviors (e.g., expiration time, error handling) are omitted but acceptable for a simple tool.

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 consists of two sentences, with the first sentence immediately stating the main action. No extraneous information. Very efficient.

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?

Given no output schema, the description should mention the return value (e.g., draft ID or status). It also lacks detail on parameter usage. It is too brief for an agent to fully understand the tool's behavior without additional documentation.

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 coverage is 0% and the description provides no explanation of the parameters, especially the optional ones (newArrivalDate, newDepartureDate, newPeopleNumber), which seem to conflict with the 'cancellation' focus. The agent cannot infer their purpose from the description.

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 uses a specific verb ('Fetch' and 'create') and clearly identifies the resource (reservation cancellation draft). It distinguishes from the sibling tool 'confirm_cancellation' by noting that confirmed cancellation remains browser-handoff only.

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 implicitly guides usage by stating that confirmed cancellation is not handled by this tool, implying it is only for preparation. However, it does not explicitly list when to use this versus other similar tools like confirm_cancellation.

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