fa_get_flights

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds that the tool returns recent, current, and scheduled flights, providing useful behavioral context beyond the annotations. No contradictions.

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, no wasted words. The most important information (purpose and input types) is front-loaded, making it easy for an agent to quickly understand the tool.

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 6 parameters and no output schema, the description covers the core purpose and the main parameter semantics. It could mention paging (max_pages, cursor) or the return format, but the sibling tools and annotations provide some context. It is mostly complete for the agent's decision-making.

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%, so the baseline is 3. The description adds meaning by explaining the three types of ident (designator, registration, fa_flight_id) and implying the return types, which helps the agent understand the purpose of the main parameter better than the schema alone.

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 it gets flights for an ident (flight designator, registration, or fa_flight_id) and specifies it returns recent, current, and scheduled flights. This distinguishes it from siblings like fa_get_flight_history or fa_get_flight_position.

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 explains the types of identifiers accepted and the time scope of returned flights, giving good context for when to use this tool. However, it does not explicitly contrast with other similar tools like fa_search_flights or fa_get_operator_flights, which could help an agent choose between them.

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