Find Movie Showtimes

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

The description states 'read-only', which matches the readOnlyHint annotation, but does not add significant behavioral context beyond that. The annotation already covers safety, so the description adds only the scope constraint (one movie/date) and location preference. No contradictions with annotations.

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 with no redundancy. Every word serves a purpose: verb, resource, scope, constraints, and a preference. No fluff.

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 8 parameters and no output schema, the description covers core functionality but omits details about pagination (the page parameter exists but is not explained), return format, or error conditions. It is minimally adequate but leaves gaps for a complex search tool.

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%, so the schema already documents all 8 parameters. The description adds value by explaining the location requirement and preference (zip vs lat/long), but does not enhance understanding of other parameters like page, format, or chainCode. Baseline 3 is appropriate.

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 verb 'Find', the resource 'read-only Fandango showtimes', and scopes it to 'one movie across nearby theaters on one date'. This distinguishes it from sibling tools like fandango_theater_showtimes which focus on a specific theater.

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 mentions requirements ('Requires either zip or lat/long') and a preference ('lat/long is preferred when both are present'), but does not provide guidance on when to use this tool versus alternatives (e.g., fandango_theater_showtimes or fandango_scan_movie_availability). No when-not conditions are given.

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