fa_list_airports

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

Annotations already provide readOnlyHint and openWorldHint. Description adds the paging behavior and cursor usage, but does not reveal additional behavioral traits such as rate limits, data freshness, or response structure. This is adequate given the simple read-only nature.

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 short sentences, front-loaded with purpose. Every word is functional with no redundancy. Excellent conciseness.

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?

Description covers the core purpose and paging, but omits what data is returned (e.g., airport codes, names) since no output schema exists. For a simple list tool, this is minimally adequate but could be improved with a brief note on response content.

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 100%, with detailed descriptions for both cursor and max_pages (including billing context). The description only adds 'Use the cursor to page through', which does not surpass the schema's own semantics. Baseline score of 3 is appropriate.

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?

Description clearly states 'List airports known to AeroAPI' with verb 'List' and specific resource 'airports'. It distinguishes from sibling fa_get_airport by implying a collection rather than a single item. The mention of paging clarifies the scope.

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?

Description lacks explicit guidance on when to use this tool vs alternatives like fa_get_airport (for single airport). It only provides paging instructions ('Use the cursor to page through'), but no context on selection criteria or exclusions.

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