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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing behavioral beyond that (no auth, rate-limit, or freshness caveats); 'snapshot metadata' hints at point-in-time data but is not explained.

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?

A single front-loaded sentence with no filler; the resource and the lookup key are both established immediately. Every clause (returned metrics, key format) carries information.

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-parameter read-only tool with full annotation coverage, the definition is nearly sufficient; enumerating the returned metrics partly compensates for the absence of an output schema. The remaining gap is the lack of any sibling differentiation or note on what 'oTDH' means, which get_otdh_methodology presumably covers.

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% for the single 'slug' parameter, and the schema already documents it as an AB5D artist slug with an example. The description only restates 'by AB5D artist slug', adding no format or scope detail beyond the schema, so the baseline of 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?

The description gives a specific verb ('Get') and resource ('one artist's oTDH') and enumerates the returned metrics, so its purpose is unambiguous. It stops short of distinguishing itself from adjacent siblings such as get_artist_collector_tdh or list_artist_otdh, only implying the single-artist scope via 'one artist's'.

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 implied rather than stated: 'one artist's' suggests this is the singular lookup counterpart to list_artist_otdh, but no alternative is named and no when-to-use or when-not-to-use condition is given. An agent must infer routing from the name pattern alone.

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