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

Annotations already cover readOnly/idempotent/no-destruction, and the description adds the single most important behavioral caveat: dates, showtimes and prices are absent and must be retrieved via the returned webtic.it links. That prevents a very plausible misuse of the tool.

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?

Three sentences: purpose and payload first, use cases second, scope limitation last. No filler and nothing buried.

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?

An output schema covers return values and annotations cover safety, so the remaining burden on the description is scope and data limitations, both of which are stated. An agent has everything needed to call it correctly and to know what it will not get back.

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?

There is only one parameter and schema description coverage is 100%, with venueId already documented as 'id as returned by search_venues'. The description implies the parameter means a cinema or theatre but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ('returns everything currently on sale at a specific cinema or theatre') and enumerates the payload: events, their versions, per-item links, and the venue program link. An agent can distinguish this from search_events and get_event_details without opening a schema.

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?

Gives concrete usage phrasings ('what's on at cinema X', 'what does theatre Y have') and draws a hard boundary around the data ('currently on sale, not when'). It does not explicitly name the sibling to use for showtimes/prices beyond pointing at webtic.it links, so the alternative routing is only partial.

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