get_showtimes

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

No annotations are provided, so the description must fully carry the behavioral disclosure burden. It only states the core fetch action, providing no context on response format, empty results, or side effects. This is minimal disclosure beyond what the tool name already implies.

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, efficient sentence with a clear verb and object. It is front-loaded and contains no filler 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 a simple tool with fully described parameters and an output schema, the description captures the core function. However, it omits the date aspect from the description and does not mention error handling or empty results, though these are likely covered by the output schema.

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% for all three parameters, so the baseline is 3. The description adds no extra parameter meaning and actually omits the required 'date' parameter, though the schema fully documents it.

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 the specific verb 'Fetches' with the resource 'available showtimes for a specific movie and location.' This clearly distinguishes it from sibling tools like get_now_showing (lists movies) or get_seat_map (seat availability).

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 (fetch showtimes for a movie/location) but does not explicitly state when to use it instead of siblings, nor any prerequisites or exclusions. It lacks guidance on process flow, such as first obtaining a movie_id via get_now_showing.

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