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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered. The description adds that data comes from a public page and that rows are ranked, which is modest extra context, but it says nothing about pagination, result volume, or refresh/freshness behavior.

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 efficient sentence with the key action and source front-loaded; nothing is wasted. It could still be slightly tightened or extended to earn a 5.

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 exists, so return-value documentation is not required, and annotations cover the safety profile. However, with two undocumented parameters at 0% coverage and no usage routing, the definition is only minimally complete for a data-retrieval tool.

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 description coverage is 0% and both parameters (sort, sortDir) are undocumented in the schema. The description references 'ranked' rows, hinting at ordering, but never explains the sort/sortDir parameters or their accepted values, so it fails to compensate for the coverage gap.

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?

States a specific verb (returns) and resource (ranked franchise rows) with source context (Box Office Mojo's public /franchise/ page). It is clear what the tool does, but it does not differentiate from the sibling 'boxofficemojo_franchise' (singular), which likely returns a single franchise's details — the list-vs-detail distinction is left to inference.

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?

There is no when-to-use guidance and no mention of alternatives such as boxofficemojo_franchise or boxofficemojo_brands. The agent is left to guess which franchise/brand tool to pick.

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