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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile needs no restating. The description earns credit by disclosing what comes back — seat counts by cabin, per-map last-checked date, and page links — which matters because no output schema exists. It stops short of any pagination or result-cap behavior for what could be a large catalog.

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?

One sentence, zero filler, and the broadest scope is front-loaded before the narrowing option. Every clause carries information the agent would otherwise have to guess at.

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?

For a one-optional-parameter, read-only list tool with full schema coverage and no output schema, this covers purpose, scope, and return fields adequately. The remaining gap is operational: nothing about ordering, limits, or how many seat maps a full listing yields.

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% and the single 'airline' parameter is documented with accepted forms (IATA code, slug, UUID). The description only reinforces that the parameter is an optional narrowing filter ('or one airline's'); it adds no new format or matching semantics beyond the schema, so baseline 3 applies.

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?

States a specific verb (list) and resource (airline seat maps) with explicit scope: all seat maps or one airline's. The singular sibling get_seatmap is implicitly distinguished by the 'every ... (or one airline's)' framing, but it is never named, so the differentiation is inferential rather than explicit.

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 parenthetical '(or one airline's)' implies the filter use case, which is reasonable guidance, but there is no explicit when-to-use statement, no exclusion of alternatives such as get_seatmap for a single known seat map, and no mention of result-volume or pagination behavior for a full catalog listing.

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