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

No annotations are provided, so the description fully bears the burden. It discloses that the tool is a read operation, returns multiple categories of movies, and includes specific fields. It does not mention rate limits or authentication, but for a list tool, these details are acceptable.

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 a single paragraph of three sentences, front-loaded with the core purpose and condition, then details on categories and returned fields. Every sentence adds value with no redundancy.

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?

Without an output schema, the description lists key returned fields (title, genres, TMDB rating, runtime, detail URL) and explains the status filter. It does not address pagination beyond the limit parameter or default ordering, but overall it provides sufficient context for an AI to use the tool correctly.

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 100% with both parameters described. The description adds value by explaining the meaning of the 'status' enum values (e.g., 'now_showing' = films with upcoming showtimes) and mentioning that 'limit' controls max return count, reinforcing the schema's explanations.

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 states the tool lists movies available in the neighborhood, specifying three categories (now-showing, coming-soon, streaming) and the fields returned (title, genres, TMDB rating, runtime, detail URL). This clearly distinguishes it from sibling tools like list_events or list_products, as it is movie-specific.

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 includes a precondition ('only on sites with movies_enabled') and implies usage for retrieving movie listings. While it does not explicitly state when not to use the tool or list alternatives, the context and name make it clear that this is for movies, not other entities.

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