track_flight

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

No annotations are provided, and the description only states it 'tracks a flight' without detailing behavior such as output format, real-time updates, or limitations. The burden of disclosure is not met.

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 brief and front-loaded with the main purpose. Every sentence is necessary and adds value, with no redundant or extraneous information.

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 no output schema and no sibling differentiation, the description lacks completeness. It explains inputs but not outputs or how the result should be interpreted, which is insufficient for a tracking tool.

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 schema has 0% description coverage, but the description adds value by explaining each parameter's purpose and providing example values (e.g., 'DLH400', '3c6752'), helping the agent understand expected input.

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 clearly states the tool tracks a specific flight by callsign or ICAO24 address, using a specific verb and resource. It distinguishes from siblings like 'track_live_flights' which implies tracking multiple flights.

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 specifies that at least one of two parameters must be provided, but it does not provide guidance on when to use this tool versus alternatives like 'track_live_flights' or other flight tools.

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