get_live_flights_positions_light

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

No annotations are provided, so the description carries full burden. It discloses the important constraint that at least one non-limit parameter is required, which is valuable. However, it does not clarify what 'light' means, potential response limitations, or any other behavioral characteristics.

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 compact: one purpose sentence, an important note, and a list of parameter names. The list is long but necessary to convey valid search parameters. It front-loads the main purpose and wastes no words.

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 16 parameters, no annotations, and no output schema, the description provides the key invocation constraint and hints at return content (latitude, longitude, speed, altitude). However, it does not explain the 'light' vs 'full' distinction or the response structure, leaving some ambiguity.

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 description coverage is 100%, so all 16 parameters already have detailed descriptions. The tool description merely lists parameter names and notes 'limit' as an exception, adding no new semantic information beyond what the schema provides. Baseline 3 is appropriate.

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 it returns real-time aircraft flight movement data with specific fields (latitude, longitude, speed, altitude), using the specific verb 'Returns'. It identifies the resource precisely, but it does not explicitly distinguish from the sibling 'full' variant beyond the name 'light'.

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 provides explicit usage guidance: at least one search parameter (other than limit) must be provided and non-empty, and it lists all acceptable filter parameters. It does not mention alternatives or when to prefer the 'full' variant, but the context is clear for correct invocation.

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