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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description does add real context beyond them — collector rows are paginated and can reach thousands of entries for Raster-indexed oeuvres — which explains data volume and the need for limit/offset, but it says nothing about auth requirements, ordering, or end-of-results 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 verb and identifying key, and the second sentence carries non-redundant pagination rationale. No filler and nothing buried.

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 thin schema coverage, the description should at least sketch what a 'collector TDH register' row contains and whether results are ordered; it only says rows are paginated addresses. Adequate to call the tool correctly, but the return contract remains largely unspecified.

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 only 33%: 'slug' is documented in-schema while 'limit' and 'offset' are not. The description's pagination sentence signals that these control paging, partially compensating, but it never states defaults, maximums, or what happens when offset exceeds the row count.

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 and resource ('Get one artist-specific collector TDH register by AB5D artist slug'), and the 'one ... by slug' phrasing implicitly contrasts with the list variant. It does not explicitly distinguish itself from siblings like get_artist_otdh or list_artist_collector_tdh, so it falls short of a 5.

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 only implied: the 'one register by slug' framing suggests single-artist lookup while pagination suggests browsing large sets, but no alternative tool is named and no when-not-to-use condition is given. An agent must infer the get-vs-list split from the sibling names alone.

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