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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavioral context the annotations lack: what oTDH measures, its 1,000 scale, and that it is price-independent and neutral to edition size, project count and release date. It stops short of stating the sort direction or pagination behavior.

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 sentences, front-loaded with the action and scope; the second sentence defines oTDH, which earns its place by making the ranking interpretable. Slightly heavy on metric definition for a list operation, but nothing is wasted.

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 and no annotations covering return shape, the description should describe what a record contains (rank, artist, score) and whether ordering is descending. It conveys the metric's scale but not the record structure, leaving a real gap for a list tool.

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 0%, so the description must carry the load. The phrase 'a limited leading subset' does add meaning to `limit` beyond the bare integer/min/max/default in the schema, implying it selects the top-ranked entries rather than an arbitrary page. It still omits the default of 25 and the 1-308 bounds behavior.

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 (List) and resource (ranked oTDH records) plus scope (all 308 AB[500] artists or a limited leading subset), which is concrete and unambiguous. It never names the sibling get_artist_otdh or list_artist_collector_tdh, so the agent must infer the single-vs-multi distinction from scope wording alone.

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?

No when-to-use guidance is offered: nothing says when to prefer this list over get_artist_otdh, list_artist_collector_tdh, or get_otdh_methodology. The description defines the metric but leaves routing to the agent.

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