change_voice

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

With no annotations provided, the description carries full responsibility for behavior. It discloses that the change persists across restarts, affects the listener daemon, applies to future speak/announce calls, and that duplicate voices are refused to prevent indistinguishable speakers. This dramatically exceeds baseline explanation.

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?

The description is organized in clear sections with the proactive sentence first, followed by practical details and then argument semantics. Every sentence adds relevant information; there is no redundancy or filler.

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?

This is a persistent state-changing tool with a lightness of given structured metadata. The description covers side effects, persistence, usage context, the valid arguments, and the duplicate-owner failure behavior. There is enough to invoke intentionally and 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?

The schema provides no parameter descriptions (0% coverage), so the description is the only source of meaning. It explains voice_id as the voice to switch to and elaborates on speaker, including its use for named SPEAKER-defined personas and the duplicate-refusal behavior. It could be slightly stronger on voice_id's allowed values, but overall it compensates well.

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 a specific verb and resource: 'Deliberately switch this agent's speaking voice from now on' and details the state change. It distinguishes itself from the sibling speech tools by explicitly stating that speak carries no voice information and that this is the only way to change how one sounds.

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 gives clear context: use this call when the user asks for a voice change, use list_voices to see options, and don't expect speak/announce to carry voice information. This effectively tells the agent when to use this tool versus its siblings.

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