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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine value by revealing that the role is selected automatically as the 'least-used' one rather than chosen by the caller, but it says nothing about whether repeated calls return the same role, what 'temporary' means, or how the evidence requirements are shaped.

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 zero padding. It is efficient, though the compression is part of why key behavioral details are absent.

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, the description is the only source of return-value information, and it names the two returned pieces (role, evidence requirements) without structure or format. It also omits how the assignment connects to downstream siblings such as submit_voice or validate_voice, leaving the agent to guess the workflow.

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% — the single parameter is documented only by a 28-value enum with no explanation. The description compensates partially by identifying it as a published song, implying the enum values are song slugs, but gives no guidance on unpublished/unknown titles or slug formatting.

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 (receive) and a specific resource (the least-used critical role plus its evidence requirements), scoped to one published song. It is distinguishable from generic task tools, but it never names or contrasts with siblings like next_task or research_queue, and 'critical role' remains domain jargon an agent must infer.

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?

There is no when-to-use guidance and no mention of alternatives, despite a crowded sibling set (next_task, research_queue, list_voices, leave_quick_voice). The only contextual cue is 'for one published song', which describes the input, not the situation that should trigger this call.

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