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

No annotations are provided, so the description must carry the full burden. It discloses the condition (movies_enabled) and the types of movies returned, but does not explicitly state that the operation is read-only, nor does it mention any authentication or rate limits. The described behavior is consistent with a read-only list, but transparency is adequate but not exceptional.

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 (three sentences) and front-loaded with the main purpose. Every sentence adds meaningful information, though it could be slightly more structured (e.g., bullet points for the return fields).

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?

The description covers the return fields (title, genres, TMDB rating, runtime, detail URL) and the movies_enabled condition. However, it lacks information on pagination (how to get more than 'limit' results) and error handling if the site does not have movies_enabled. Given no output schema, the description provides sufficient but not comprehensive completeness.

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%, but the description adds value by explaining the enum values (e.g., 'now_showing' = films with upcoming showtimes at local cinemas) and the meaning of the status filter beyond the enum names. This enriches the parameter understanding.

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 lists movies available in the neighborhood, with specific categories (now-showing, coming-soon, streaming) and a condition (only on sites with movies_enabled). It is distinct from sibling tools like list_events or list_blog_posts.

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 explains what the tool does but does not provide explicit guidance on when to use it over alternatives like list_events or search_places. Usage context is implied by the movie focus, but no when-not or exclusion criteria are stated.

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