get_flight

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

Description states it's a retrieval operation ('Get'), implying no side effects. With no annotations, it carries full burden. It specifies 'most recent' but doesn't explain chronological ordering, error handling (e.g., no matching flight), or whether the tool requires authentication. Could add more detail on behavioral guarantees.

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?

One clear sentence plus concise parameter description. No fluff or repetition. Front-loaded with action and purpose.

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?

For a simple tool with one param and output schema, description covers what input is expected and what to get back ('most recent flight leg'). Minor gaps: doesn't specify whether 'most recent' is based on departure time or schedule, or if multiple legs exist per flight.

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 provides no description (0% coverage). The description adds meaning: flight_no is case- and space-insensitive. This is valuable extra info beyond schema type. Single parameter fully described.

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 states a specific verb ('Get'), resource ('most recent flight leg'), and criterion (matching flight number). Example 'UA194' clarifies format. Distinguishes from siblings 'flight_stats' and 'list_my_flights' by implying a single recent leg lookup.

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 implies usage for retrieving the most recent leg of a specific flight, but lacks explicit guidance on when to use this tool versus alternatives like 'list_my_flights' (for listing all flights) or 'flight_stats' (for statistics). No exclusions or prerequisites stated.

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