convert_nnumber

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

Discloses automatic detection, returns both forms plus 'mode' flag. No annotations provided, so description carries full burden. For a simple conversion, it adequately covers behavior.

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 sentences plus a usage note; no wasted words. Front-loaded with purpose and ends with practical usage context.

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?

Complete for a simple one-parameter tool: explains input format, output fields, and use case. No output schema needed given straightforward return values.

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 only parameter 'identifier' is fully explained in description: accepts N-number (N + digits/letters) or ICAO24 (6-char hex). Compensates for 0% schema description coverage.

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 function: convert between FAA N-Number and ICAO24 hex address. It specifies the verb 'Convert' and the two identifiers, distinguishing it from sibling tools like lookup_aircraft_state.

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?

Describes automatic input detection based on format (N-prefix vs 6-char hex). Provides use case for cross-referencing aviation data. No explicit exclusions needed given distinct siblings.

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