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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered, but the description adds no behavioral context at all - no indication of the data source, granularity of bins, or whether ratings are live/aggregated. An output schema exists, yet nothing explains the shape of the distribution.

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?

A single five-word fragment, front-loaded and free of filler. It is appropriately sized for a simple read endpoint, though the terseness is close to under-specification rather than exemplary brevity.

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?

An output schema is present, so return-value explanation is not required, and the sole required parameter is documented. Still, for a tool whose whole value is the histogram shape, the description provides no context about what the distribution contains, leaving the agent to rely entirely on structured fields.

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?

Only one parameter (slug), and the schema documents it at 100% coverage with a concrete example ('parasite-2019'). The description adds no additional parameter meaning, which is the expected baseline when the schema fully covers the input.

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?

Names a specific resource (Letterboxd film) and the exact aspect being retrieved (rating distribution), so an agent knows it returns a rating breakdown rather than general film metadata. It lacks a verb and does not distinguish itself from siblings like letterboxd_film or letterboxd_film_reviews, but the purpose is unambiguous.

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?

No guidance on when to use this versus letterboxd_film, letterboxd_film_reviews, or letterboxd_film_similar. The agent must infer that this tool is for the rating histogram specifically, with no stated conditions or alternatives.

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