Domestic flight seats

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing that TDX queries the airline live, that calls can take up to 30 s, and that UNI Air has request limits — operationally critical for an agent. It stops short of saying what happens on timeout or unsupported airline/date, which would complete the picture.

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?

Every clause carries information — scope, output tiers, latency, rate limit, batching rule, example. The opening sentence is somewhat convoluted ('per cabin when the airline says'), which costs a bit of front-loaded clarity, but nothing is padded.

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?

With no output schema, the description correctly compensates by enumerating the three availability levels and their per-cabin granularity. Combined with the latency and rate-limit warnings, an agent has enough to invoke it correctly; only error/failure behavior is unaddressed.

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 already 100%, so the baseline is 3; the description lifts this by giving a concrete worked example ('AE1273', '2026-11-02') and noting the airline-code requirement. It doesn't elaborate on the 'default: today' timezone beyond what the schema already states.

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 resource (seat availability per cabin) with scope qualifiers (only domestic AE/B7/DA flights) and names the exact output categories (available, fewer than 5 left, sold out). An agent can immediately distinguish it from siblings like thsr_seats or flight_status.

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 says to call it for one flight at a time and warns that UNI Air permits few requests, which shapes how an agent should batch. It does not, however, contrast the tool with flight_status or flight_schedule, so the routing guidance is conditional rather than complete.

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