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

Annotations already mark it read-only, idempotent and non-destructive, and the description still adds substantive behavior: it is disabled while the protection ladder is raised returning tool_disabled/ladder_L1, unclassified sections return present:false, and results carry a stale flag. It also discloses the credit cost (attribution.line), an ambiguity stop condition, and that untrusted_text is display-only.

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?

Front-loaded with the served/withheld distinction, then Use/Inputs/Returns/constraints in a scannable order. The closing credit, ambiguity and untrusted_text boilerplate is dense but each item is operational information an agent must honor.

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?

With no output schema, the description compensates by naming the returned fields (data.rows[] rank/name/slug/emergenceTier/momentumTier, snapshot_date, stale) plus auth and degradation modes. It stops short of explaining what emergenceTier/momentumTier mean or what 'crate classifies' actually implies for the withheld sections.

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 description coverage is 100% and the schema already documents the section enum, the 1–50 bound, the default, and the range_too_large failure. The description restates the same enum and range without adding syntax or interaction detail, so the baseline 3 applies.

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 resource (hosaka's tastemaker index) and sectioned scope, and makes clear which sections are served versus withheld. It never names list_ones_to_watch, which covers the same default section, so the agent gets no explicit differentiation from the most confusable sibling.

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?

"Use: up-and-coming artists, or who moves a scene" gives intent but no when-not guidance and no alternatives, even though list_ones_to_watch and list_breakouts are obvious substitutes. The withholding rule for unclassified sections is a real usage constraint, which lifts it above pure implication.

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