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

No annotations are provided, so the description bears full responsibility. It clearly describes the three categories of returned films and the included fields (title, genres, rating, etc.), which is sufficient for a non-destructive list 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?

Two sentences that efficiently convey purpose, scope, and output fields. No fluff; every piece of information 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 low complexity (no required parameters, no output schema), the description fully covers what the tool does, what it returns, and the relevant filter options. It is complete for an agent to decide and invoke 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 decent parameter descriptions. The description adds value by elaborating on what each status filter returns (e.g., 'now_showing = films with upcoming showtimes at local cinemas'), complementing the 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 specifies a concrete verb ('list') and resource ('movies available in this neighborhood') and clearly distinguishes its scope (e.g., actual showtimes, streaming availability) from sibling tools that handle bookings or events.

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 mentions the feature flag ('only on sites with movies_enabled') and the status filter options, providing clear context. However, it does not explicitly state when to prefer this tool over related siblings like get_showtimes or list_events.

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