fa_search_flight_positions

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

Annotations already mark it as readOnly and openWorld. The description adds context about live data and position points but does not exceed the transparency provided by annotations. No contradictions.

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?

Two sentences plus a clear example. Front-loaded with the core function. Every element contributes meaning; no 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?

The description covers the key aspects: what the tool returns, the query syntax, and an example. Paging parameters are in the schema, so they don't need to be repeated. A mention of the live nature is present. Minor improvement could be stating that it complements other search tools, but overall sufficient.

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 100%, providing a baseline of 3. The description adds value by including an example of the query format, which supplements the schema's description of the query parameter. This helps agents construct correct queries.

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?

Description clearly states the tool searches live flight positions using a structured query language. It distinguishes itself from siblings like fa_search_flights_advanced by specifying it returns position points, not flight summaries. The example further clarifies the purpose.

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?

Explicitly specifies the structured query language grammar and warns against using the simplified syntax. Provides an example and implies different usage from other search tools by contrasting output types. However, it does not explicitly list alternative tools or when to use them.

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