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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the core safety profile is known. The description adds context about oTDH being 'price-independent' and 'current uninterrupted collector holding duration', which is domain context but not a behavioral trait like rate limits, pagination, or ordering specifics. The term 'ranked' implies sorted, but details are absent.

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 two sentences, front-loaded with the core action and scope, followed by a concise definition of the domain term. Every sentence contributes meaningful information without redundancy or fluff.

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 list tool with one optional parameter and no output schema, the description provides enough context to understand the purpose and the meaning of oTDH. It is missing explicit details about the return format or ordering direction, but given the low complexity and strong annotations, these are minor gaps.

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 0%, so the description must compensate. It mentions 'or a limited leading subset', which indirectly maps to the 'limit' parameter by implying that limiting the result set is possible. However, it does not explicitly state that the 'limit' parameter controls how many leading artists are returned, leaving the connection vague.

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 description states a clear verb and resource: 'List the ranked oTDH records for all 308 AB[500] artists, or a limited leading subset.' This distinguishes it from the sibling 'get_artist_otdh' by emphasizing all artists or a subset, making the list-vs-single distinction obvious. The additional definition of oTDH further disambiguates its domain.

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 description does not provide explicit guidance on when to use this tool versus alternatives. It never mentions 'use get_artist_otdh for a single artist' or any other exclusion condition. The only implicit usage is the scope ('all 308'), but no direct comparison to siblings is given.

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