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

No annotations are provided, so the description bears full responsibility. It discloses that the tool only works on sites with movies_enabled, and details the return categories (now-showing with showtimes, coming-soon, streaming). It adds value beyond the schema by explaining the behavior of the 'status' parameter.

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, no filler. First sentence sets scope and condition, second sentence enumerates return categories and included fields. Every word earns its place.

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?

Given the tool has only 2 optional parameters and no output schema, the description explains the return fields (title, genres, TMDB rating, runtime, detail URL). It is nearly complete, though missing default ordering or pagination details.

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%, and both parameters have descriptions in the schema. The description adds extra context for the 'status' enum values, explaining what each means (e.g., 'now_showing' = films with upcoming showtimes). This adds value beyond the bare schema.

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 three categories (now-showing, coming-soon, streaming). It specifies the resource (movies) and action (list), and distinguishes from siblings like list_events or list_products.

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 provides a clear purpose but does not explicitly state when to use this tool versus alternatives like list_events or get_showtimes. The usage context is implied but lacks direct exclusions or comparisons.

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