voicebox_speak

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

Describes immediate playback and auto-profile fallback, but lacks details on side effects, blocking behavior, or success indicators. No annotations to compensate.

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, no wasted words. Each sentence adds value: core purpose and differentiation/simplification.

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?

Given the 5 parameters (all described in schema), existing output schema, and many siblings, the description is sufficient for basic usage and differentiation. Could mention the text character limit but it's in schema.

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 covers all 5 parameters (100% coverage). The description adds meaningful context: explains that omitting 'profile' triggers automatic selection with a fallback chain, which enhances understanding.

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 clearly states the tool's action ('Speak text immediately — plays on the user's speakers') and distinguishes it from the sibling 'voicebox_generate', providing a specific verb and resource.

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?

Explicitly notes when to use this over 'voicebox_generate' (simpler, auto-profile selection) but does not mention other alternatives or exclusions.

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