flight.status

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

With no annotations, the description carries the burden of behavioral disclosure. It discloses that the tool queries by ident and returns various flight status fields. However, it doesn't mention rate limits, authentication, or whether the data is cached. It is adequate but not exhaustive.

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?

The description is two sentences, front-loading the key function and immediately providing examples. Every sentence adds value without redundancy.

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 the three parameters (one required) and no output schema, the description adequately covers what the tool does and what data it returns, listing specific fields. It lacks details on output format but is sufficiently complete for selection.

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 description adds context beyond the schema by providing examples of valid ident values (UAL1 / UA1 or tail number) and clarifying the types of queries. However, it doesn't explain the 'limit' or 'identType' parameters, though the schema provides enum for identType.

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 explicitly states it provides live flight status by flight designator or tail number, lists specific details returned (origin/destination, status, times, delays, etc.), and answers common questions. This is a specific verb+resource that distinguishes itself from siblings by its focused 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?

The description implies usage for tracking flights and answering specific questions like 'where is this flight, is it delayed, when does it land' but does not explicitly state when to use this tool over alternatives or when not to use it.

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