get_seat_map

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

With no annotations provided, the description carries the burden of behavioral disclosure. The verb 'Displays' clearly signals a read-only operation, and mentioning 'available and reserved seats' gives insight into what the user will see. It does not state side effects, but the non-destructive intent is apparent.

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 a single sentence that directly states the tool's purpose and scope. It is front-loaded with the action and object, containing zero wasteful 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?

This is a simple tool with one parameter, an output schema exists (so return values need not be explained), and the description fully covers the essential context: what it does and for what. No critical information is missing for an agent to select and invoke it correctly.

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?

The input schema already covers the single parameter showtime_id with a clear description and example (100% coverage). The description only restates that it is for a specific showtime, adding no additional semantic detail beyond the schema.

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 uses a specific verb ('Displays') and resource ('available and reserved seats') for a specific showtime, clearly distinguishing this tool from siblings like get_showtimes (listing times) and book_seats (booking). It precisely explains what the tool does without ambiguity.

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 implies usage in the context of viewing seat availability for a showtime, but it does not explicitly state when to use this versus alternatives or mention any prerequisites (e.g., 'use before booking'). There is no exclusion or alternative reference, so the guideline is only implied.

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