calculate_flight_distance

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

No annotations are provided, so the description carries full burden. It does not disclose output units (e.g., kilometers/miles), formula used (e.g., Haversine), or Earth radius assumption. For a simple calculation, this is adequate but not transparent. An output schema exists but is not referenced.

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 two sentences, front-loads the purpose, and includes a useful pointer to the sibling tool. Every sentence is meaningful and there is no wasted text.

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 4-parameter tool with output schema and no annotations, the description covers the core function but omits output details (units, precision) and does not explain edge cases (e.g., poles, antimeridian). The pointer to list_bundles adds slight completeness.

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 100%, so the schema already documents each parameter (e.g., 'Departure latitude'). The description adds no new parameter-level meaning beyond what the schema provides.

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 tool's purpose: calculate great-circle distance between two coordinates. It uses a specific verb 'Calculate' and resource 'great-circle distance between two coordinates', and distinguishes from siblings by pointing to list_bundles for related 'voyage' calculators.

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 explicitly says 'See list_bundles for related voyage calculators', providing clear context for when to use an alternative tool. However, it lacks explicit when-not-to-use guidance or coverage of other related distance calculators among siblings.

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