track_live_flights

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

No annotations are provided, so the description must cover behaviors. It describes the two modes (global vs bounding box) and the limit, but omits details on data freshness, rate limits, or delays.

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 structured with a summary, mode explanation, and a clear args list. Every sentence adds value, with no fluff.

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 5 parameters, no required ones, no output schema, and no annotations, the description covers usage and parameter semantics well. Missing output format details, but the tool name implies live flight data.

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 0%, but the description explains all 5 parameters: lamin, lomin, lamax, lomax with geographic meaning and an example, plus limit with default and maximum.

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 live flights globally or in a bounding box. It uses specific verbs ('verfolgen') and a resource ('Aktuelle Flüge'), and distinguishes from siblings like 'track_flight' for single 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 explains when to use coordinates vs. none, and mentions the limit parameter's default and maximum. Although it does not explicitly exclude alternatives, the context implies 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.