find_nearest_airport

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

No annotations provided, so description carries full burden. It explains sorting by distance, default distance, and inclusion of nearby cities. Does not mention return format or API limitations, but for a read-only query tool this is sufficient.

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?

Front-loaded with a bold 'TRIGGER' instruction, then concise details. Every sentence adds value. Slightly verbose but efficient and well-organized.

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?

Covers trigger, input requirements, usage relative to sibling tools, and mentions output order (sorted by distance). Lacks explicit return structure but acceptable for a straightforward query tool.

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 has 100% parameter descriptions. The description adds value by clarifying that 'distance' is in km and defaults to 50, and advises using search_airport_code to resolve place names to coordinates. Does not explicitly describe 'lang' but that is fully covered in schema.

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 it finds nearest airports to a coordinate, sorted by distance. It distinguishes from siblings like search_airport_code by specifying coordinate input and automatic trigger for 'closest airport' queries.

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 instructs to use automatically when user asks for nearest airport, provides use cases, and advises to use search_airport_code first if user names a place instead of coordinates. Also specifies fallback for airport code requests.

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