Read Theater Calendar

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

Annotations already mark as read-only and open-world. Description adds that tool returns dates with showtimes, giving specific behavioral insight beyond 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?

Single sentence, front-loaded, no extraneous words. Every part adds value.

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?

No output schema, but description adequately explains output (dates with showtimes). With openWorldHint, volatility is acknowledged. Lacks only details like pagination or format.

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 covers 100% of parameters with descriptions. Description doesn't repeat parameter details but adds context that theaterId identifies a single theater and startDate is optional.

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?

Description clearly states verb 'Read', resource 'showtime calendar for one theater', and output 'which dates currently have showtimes'. It distinguishes from siblings like fandango_theater_showtimes and fandango_movie_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?

Description indicates use case: reading calendar for one theater to see dates with showtimes. It doesn't explicitly exclude other uses, but sibling names provide context for differentiation.

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