fa_count_flights

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

Discloses that the tool only returns a count, not flights, and explains query syntax. Annotations already indicate readOnly; description adds return type and usage pattern.

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 example, front-loaded with purpose, no unnecessary words.

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?

Given tool simplicity (one param, no output schema, readOnly annotations), the description fully covers functionality, syntax, and return value.

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 covers parameter with description, but description provides concrete example and clarifies the syntax is same as fa_search_flights, adding value beyond 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?

Description uses specific verb 'count' and resource 'flights', clearly states it returns a count without returning flights, and distinguishes from search tools by syntax reference.

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 mentions the syntax (simplified -key value) and contrasts with fa_search_flights_advanced, giving guidance on when to use this tool. Could be improved by stating 'when only count needed'.

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