get_flight_summary_light

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

With no annotations, the description carries the full burden and adds useful behavioral context: data availability start date, real-time/historical support, and the IMPORTANT constraint about additional search parameters. It does not disclose pagination or output structure, but for a read-only summary tool this is adequate.

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 three sentences plus a highlighted IMPORTANT note. It front-loads the purpose, then provides data availability and essential usage constraint, with no wasted 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 12 parameters and no output schema, the description adequately explains purpose, data range, and usage requirements. It does not clarify what 'light' means versus the full sibling, but the description covers enough for an agent to select and invoke the 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?

Schema coverage is 100%, so baseline is 3. The description adds the global constraint that at least one additional search parameter (other than sort/limit) must be provided, which is not in the schema. This provides value beyond the schema descriptions.

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 returns key timings and locations of takeoffs/landings along with primary flight/aircraft/operator info. It is specific but does not explicitly differentiate from the sibling get_flight_summary_full, so it lacks sibling distinction.

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 clear context: real-time and historical data, availability starting 2024-04-07, and required datetime parameters plus at least one additional search parameter. It does not explicitly state when to use this light version vs the full version, so no exclusions/alternatives are mentioned.

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