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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool is safe. The description adds context about fetching 'real' showtimes with date range constraints (max 14-day range in parameter schema). No contradictions, but doesn't detail authentication or rate limits.

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 concise with two well-structured paragraphs. The first sentence states the core purpose, followed by clear usage examples and a summary of filters. Every sentence contributes meaning, no redundant content.

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?

While lacking an output schema, the description explains it returns 'todas las películas y sesiones disponibles,' which is sufficient for a typical cinema showtime tool. Parameter documentation covers inputs well. Minor gap: no explicit mention of ordering or pagination, but the tool is simple and domain-common.

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 coverage is 73%, so most parameters are already documented. The description adds value by listing the supported filter categories (niños, duración, puntuación, estrenos, géneros, versión, franja horaria) and referring to get_cartelera_localidad for identical filters, helping an agent understand available options.

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 retrieves ('Obtiene') the real showtimes of a specific cinema between two dates. It distinguishes itself from sibling 'get_cartelera_localidad' by focusing on a single cinema rather than a locality, and provides specific user query examples.

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?

Explicitly states when to use: when the user mentions a specific cinema or wants to know what movies are playing there. It also implicitly excludes locality-based queries by referencing get_cartelera_localidad as the alternative for that case.

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