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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely useful interpretation context the annotations cannot: what each chart marker means and the important clarification that UP/DOWN/= reflect sales range rather than chart position.

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 a single front-loaded sentence that identifies the resource first, then enumerates markers compactly. The long parenthetical is dense but every marker definition is load-bearing for interpreting the response, so little could be cut without losing meaning.

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 one-optional-parameter read tool with no output schema, the description covers what is returned (Top 50, ranked by sales, last_week_rank, markers) and the default window, which is nearly everything an agent needs. Minor omissions are the response shape (e.g., whether last_week_rank can be null) and how markers relate to the get_movers sibling.

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 100% and edition_id's format and default-to-latest behavior are already documented in the schema. The description's closing clause restates that default rather than adding new semantics, so it does not exceed the baseline.

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 UGC Chart Top 50 for a week, ranked by sales" gives a specific verb-less but unambiguous retrieval resource and states the ranking criterion, so the agent knows exactly what it returns. It does not explicitly contrast itself with siblings such as get_movers, even though the GREATEST_GAINER marker suggests partial overlap.

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?

Usage is only implied: fetch the chart for a given week, or omit the week for the latest one. There is no explicit when-to-use versus when to call get_movers or compare_creators, and no prerequisites or rate/permission notes.

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