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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds one genuinely useful behavioral detail not in the annotations: only *approved* voices are returned, so pending/unapproved entries are excluded. It says nothing about ordering, volume, or result shape.

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, front-loaded with the action and resource, with the filter and rationale trailing. Nothing is padding, though the rationale clause is doing double duty as both purpose and usage hint rather than being crisply separated.

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-optional-param read tool with full annotation coverage and no output schema, the description covers what is returned (approved voices), the filter (song), and the caller's motivation. Only minor gaps remain, such as whether results are ordered or bounded.

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 carry the parameter's meaning — and it does at a minimal level by saying the results can be 'optionally filtered to one song', conveying that the sole param is an optional filter rather than a required selector. It adds nothing about what the enum values mean or what an unfiltered call returns, so it only partially compensates.

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 (return approved critical Voices) plus an optional song filter, which is enough to distinguish it from the write-side siblings (submit_voice, leave_quick_voice). The closing clause explains the intent (avoid repeating existing criticism), though it doesn't explicitly name a sibling for contrast.

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 clause 'so a new critic can answer rather than repeat them' implies the workflow context (read this before composing a new voice), but usage is only implied. There is no explicit when-not, no naming of alternatives such as witness_read or search_corpus, and no stated prerequisites.

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