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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive/openWorld behavior, so safety is covered. The description adds useful context by disclosing what is returned (chart names and summary stats), which matters since there is no output schema, though pagination or ordering behavior is not mentioned.

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?

Two front-loaded sentences plus a compact see-also line; every part earns its place with no filler. Slightly more content than strictly necessary but well organized.

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?

For a simple read-only listing tool with no output schema, the description covers purpose, return content, and sibling routing, and annotations cover the safety profile. Nothing essential to correct invocation is missing.

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 coverage is 50%. The required 'context' parameter is thoroughly documented in the schema itself, and response_format is a self-explanatory markdown/json enum, so the description adds no additional parameter meaning. This is the baseline case where the schema carries the semantics for both parameters.

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 and resource ('List all available Noteboxd chart rankings') with concrete examples (top-rated, trending, top by brand) and even notes the return payload (chart names and summary stats). It is clearly distinguishable from siblings like chart_get and trending.

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?

The 'See also' line routes the agent to alternatives with conditions: chart_get with a slug for the full leaderboard, trending for a quick snapshot. This tells the agent where this tool fits, though it never states an explicit exclusion such as when to avoid the list view.

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