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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds no behavioral context beyond that - nothing about rate limits, data freshness, or what the daily figures represent - so it contributes essentially nothing on this dimension.

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 description is a single terse fragment. Brevity here reflects under-specification rather than efficient front-loading, since no actionable content is delivered.

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 the description still omits the date format and any usage context for a tool that requires a date argument. It is too thin to guide correct invocation.

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?

There is one required parameter (date) at 0% schema description coverage, and the description does not compensate: it never states the accepted date format or whether it is a single day. With undocumented params, the description should clarify, 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 fragment 'Box Office Mojo domestic daily box office' names the data domain and the 'daily' scope, which does distinguish it from siblings like boxofficemojo_weekend_domestic and boxofficemojo_year_domestic. However, it is a noun-phrase label with no verb, so the exact action (return daily domestic grosses for a given date) is only implied, leaving the purpose vague rather than stated.

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 alternatives such as boxofficemojo_weekend_domestic or boxofficemojo_year_domestic, and no prerequisites. The agent must infer usage from the name alone.

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