Remove Flight

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds critical context: 'deletion syncs to all devices' and a clear warning that the action is permanent and cannot be undone. This fully discloses behavioral traits beyond 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?

Description is three concise sentences plus a one-line warning. No extraneous information. The core action is front-loaded, and the parameter guidance and warning follow logically.

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 tool with one parameter and no output schema, the description covers all necessary aspects: what it does, what input to provide, and what the consequences are (permanent deletion, sync across devices). No gaps.

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?

The input schema has one parameter with a description. The description adds extra meaning by specifying 'This is the server-side UUID, not the flight number.' Schema coverage is 100%, but the description provides a valuable clarification.

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 'Remove a flight from the user's Flighty account' with specific verb ('Remove') and resource ('flight'). It distinguishes from sibling tools like flighty_add_flight or flighty_list_flights by focusing on deletion.

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?

Explicitly tells the user to provide the flight UUID from specific sources (flighty_list_flights or flighty_add_flight) and clarifies it's the server-side UUID, not flight number. A warning about permanence is included. Could add when not to use (e.g., if only want to cancel sync), but current guidance is sufficient.

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