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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world behavior, so the safety profile is covered. The description adds useful scope information (that the response includes formulas, limitations, and snapshot metadata), but says nothing about authentication, rate limits, or snapshot dating semantics beyond naming the field.

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 the action and subject leading, followed by an enumerated list of contents. It is dense but every clause maps to a distinct returned artifact; only the run-on enumeration slightly hurts scannability.

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 parameters and no output schema, the description compensates by enumerating the returned artifacts (definition, formulas, coverage, limitations, URL, metadata). Combined with annotations that cover the safety profile, an agent has enough to call and interpret this tool, though it lacks guidance on when to reach for it.

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?

The tool takes zero parameters, so there is no parameter semantics to document; baseline 4 applies. The description correctly implies no inputs are required by describing only the returned content.

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 ('Get') and a precise resource: the methodology for AB5D's artist-level OTDH metric, enumerating the exact contents (definition, formulas, coverage, limitations, discussion URL, snapshot metadata). This clearly distinguishes it from sibling tools like get_artist_otdh and list_artist_otdh, which return data rather than the metric's methodology.

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 never says when to call this versus get_artist_otdh or the list variants, nor that it is a prerequisite for interpreting those metrics. Usage is only implied by the name and the word 'methodology'. No exclusions or alternatives are offered.

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