list_showtimes

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

No annotations are provided, so the description carries the full burden. It only mentions filtering and the only_upcoming flag. It does not disclose important behavioral traits like pagination, default ordering, result limits, or what happens when no filters are applied (e.g., does it return all future showtimes?). For a list tool, this is insufficient.

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 very concise, with two clear sentences that front-load the main action and immediately follow with the optional filters. No wasted words or redundant information.

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 the tool's simplicity (3 optional params) and the presence of an output schema, the description is adequate but lacks details about default behavior, pagination, and order. An agent could use it correctly but might have questions about edge cases.

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 0%, so the description must clarify parameter meanings. It explains 'date' as ISO date and 'only_upcoming' to hide past performances. However, 'film_slug' is not defined; the agent might not know what a slug is. Partial compensation for missing 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 lists performances with optional filters. It distinguishes from sibling tools like film_history and search_films by focusing on showtimes, though 'performances' could be more specific (e.g., film showtimes).

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?

Usage is implied: use to list showtimes filtered by date or film slug, with an option to hide past performances. However, there is no explicit guidance on when to use this tool vs alternatives, or when not to use it. Siblings are different enough that context provides clarity, but the description does not directly address selection criteria.

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