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

Annotations already declare readOnlyHint=true and openWorldHint=true, which tells the agent this is a safe, network-backed read. The description adds nothing beyond that: no note on which identifier form is needed, no freshness/caching behavior, and no signal about the data returned. It does not contradict the annotations, but it contributes no behavioral context.

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?

The text is short but under-specified rather than concise. It is a bare fragment with no informative content, so brevity here costs the agent needed information instead of removing waste.

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. However, three entirely undocumented parameters and a complete absence of usage guidance leave an agent unable to invoke this tool correctly, which is the core of contextual completeness.

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) exist with 0% schema description coverage, and the description mentions none of them. It does not clarify whether id/url/path are alternative lookups, which one is preferred, or what formats are accepted, so the full documentation burden is unmet.

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?

"Box Office Mojo title detail" is essentially a restatement of the tool name (boxofficemojo_title) rather than a description of an action. It says the tool is about a 'title' and 'detail' but never states a verb or what detail is retrieved, and it does nothing to separate this from siblings like boxofficemojo_release, boxofficemojo_brand, or datasets_boxofficemojo_item.

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 prerequisites, and no mention of alternatives. With ~20 boxofficemojo sibling tools available, the agent receives zero help routing to this one.

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