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

With no annotations, the description carries the full burden, and it does well by disclosing the precondition (movies_enabled), the categories included, and the fields returned. It does not mention rate limits or side effects, but for a read-only list tool, the transparency is adequate.

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?

Two sentences, front-loaded with the main purpose, followed by precise details on what is returned. No wasted words.

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?

Despite no output schema, the description fully explains what the tool returns. It covers the prerequisite, parameter meanings, and output composition. For a simple list tool with 2 parameters, this is complete.

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 descriptions are already clear. The description adds value by explaining the output fields (title, genres, TMDB rating, runtime, detail URL) and clarifying the meaning of the status categories (e.g., 'now_showing' includes actual showtimes).

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 action ('List') and resource ('movies available in this neighborhood'), distinguishes itself with a precondition ('only on sites with movies_enabled'), and specifies exactly what categories are returned (now-showing, coming-soon, streaming). This is specific and differentiates from siblings like get_showtimes.

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 context (movie listings) but does not explicitly mention when to use this tool vs alternatives like get_showtimes or list_categories. No exclusion criteria or when-not guidance is provided, only a precondition.

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