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 safety profile is well covered. The description adds useful behavioral context by stating that the result set is fixed at all 308 records and enumerating the fields that will appear, giving the agent a concrete sense of the response shape. It does not mention authentication or pagination, but those are less important for a read-only, idempotent list operation.

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 sentence that front-loads the action and resource, then quickly provides the record count and key output fields. There is no filler, and every phrase contributes to the agent's understanding of what the tool does and returns.

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 zero parameters, no output schema, and annotations already covering the side-effect profile, the description carries a light burden. It nevertheless tells the agent exactly how many records exist and what fields each record includes, which is enough to invoke the tool and interpret the result correctly.

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?

This tool has zero parameters and 100% schema description coverage, so the description has no parameter semantics to add. For zero-parameter tools, the baseline is 4, and the description appropriately focuses on the output rather than inputs.

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 opens with the verb 'List' and names the exact resource: 'artist-specific collector TDH dashboard records.' It also adds a precise scope ('all 308') and lists the included fields, so the agent knows what this tool returns. The 'collector TDH' qualifier distinguishes it from the sibling 'list_artist_otdh' without needing to open that tool's schema.

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 implies the use case: call this tool when you need the complete set of collector TDH dashboard records with their labels, routes, URLs, and source statuses. However, it never explicitly says when not to use it or names an alternative like 'list_artist_otdh' for OTDH records, so the routing decision is left to inference.

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