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

With no annotations, the description carries the full burden. It discloses the return structure (cinema, session times, format, language) and a prerequisite (movies_enabled). The verb 'Get' strongly implies a read-only operation, and it does not hide side effects. It lacks error-case handling but is reasonably transparent for a simple query 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?

The description is two sentences, with purpose first, then return details, then a prerequisite. Each clause adds value, with no redundant information. It is well-structured and concise.

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?

For a simple read tool with two parameters and no output schema, the description sufficiently covers purpose, return format, and a prerequisite. It is slightly incomplete in explaining how to determine 'movies_enabled' or the meaning of 'this neighborhood,' but given the tool's simplicity, it is adequate. Not a full 5 due to these minor gaps.

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?

The schema covers both parameters with clear descriptions (date format, movie_slug from list_movies). The description adds minimal extra meaning beyond mapping 'given date' and 'specific movie' to the parameters. With 100% schema coverage, the baseline of 3 applies, and the description does not enhance beyond that.

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's function with a specific verb 'Get' and resource 'showtimes for a specific movie at cinemas in this neighborhood, for a given date.' It distinguishes itself from siblings by focusing on movie showtimes and specifying return fields (session times, format, language). This leaves no ambiguity about the tool's purpose.

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 by requiring a specific movie and date, and notes the prerequisite 'Requires movies_enabled on this site.' It does not explicitly mention alternatives or exclusions, such as using list_movies to find the movie_slug, but the context is clear. It provides a clear usage context without exclusions.

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