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. The description adds zero behavioral context beyond that, saying nothing about response shape, lookup semantics, or what the three locator parameters do.

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?

It is short, but the brevity reflects under-specification rather than tight structure. The single fragment is a restated title, not a front-loaded actionable statement.

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 values need not be explained, but with three undocumented locator parameters and no usage or behavioral context, the definition is not complete enough for an agent to invoke this tool reliably.

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?

Three parameters (id, url, path) all have 0% schema description coverage, and the description offers no explanation of their meaning, format, or mutual exclusivity. This is the case where the description must compensate and it does not.

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 'Box Office Mojo showdown detail.' essentially restates the tool name and adds no verb or clarifying scope. It does not explain what a 'showdown' is or what 'detail' retrieval entails, leaving an agent unable to distinguish it from the plural sibling boxofficemojo_showdowns.

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, no mention of prerequisites, and no differentiation from boxofficemojo_showdowns or other boxofficemojo detail tools. The agent is given nothing to decide whether this is the right call.

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