Get Free Seats

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real, non-obvious domain behavior beyond that: results are grouped per vehicle (carriage/bus) and per route section, and double-decker buses are treated as one vehicle with seats listed per deck — a detail an agent could easily misinterpret as separate vehicles.

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, front-loaded with the core operation, followed by one sentence that resolves a specific modeling ambiguity. No filler or 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?

Return values are covered by the output schema and all five parameters are documented, so the description only needs to frame the operation and result grouping, which it does. A minor gap remains: it does not clarify that this is an availability read with no hold placed, which matters before an agent calls create_reservation.

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 description coverage is 100%, with every parameter documented in the schema, including cross-references to get_route_detail and list_tariffs. The description adds no parameter-level meaning, 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?

Uses a specific verb (get) and resource (free seats) with an explicit scope: per vehicle offering the given seat class, per route section. This is clearly distinguishable from siblings like get_route_detail (which supplies the inputs) and list_seat_classes (which enumerates class keys).

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 itself never says when to call this versus alternatives or what prerequisite flow applies. The ordering hint exists only implicitly via the schema note that sections come from get_route_detail and seat_class comes from price_classes, so usage is inferred rather than stated.

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