blockrun_speech

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

With no annotations, the description fully discloses behavioral traits: pricing structure, model latency, voice aliases, return format (hosted audio URL with immediate download requirement), and constraints like max 22s for sound effects. It is transparent about costs and behaviors beyond what schemas provide.

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 well-structured with sections for actions, models, voice aliases, and return value. Every sentence adds value, though it is relatively long. Could be slightly more concise, but overall efficient for the complexity.

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 9 parameters, no output schema, and no annotations, the description covers all essential aspects: actions, models, pricing, voice aliases, return format, and parameter constraints. It is complete for an AI agent to correctly select and invoke the tool.

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 coverage is 100%, so baseline is 3. However, the description adds significant value: it explains pricing per model, lists voice aliases with defaults, and provides example prompts. It enriches the schema with real-world context, justifying a score above baseline.

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 defines the tool's three actions (speak, sound_effect, voices) with specific verb+resource combinations. It distinguishes from sibling tools by focusing on ElevenLabs voice generation, while siblings like blockrun_chat, blockrun_image, etc., handle different modalities. Examples and default behavior are provided.

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 explicitly states when to use each action, provides pricing details (per char/rate, min cost), and includes examples like 'speak this with the sarah voice'. It also explains model choices for different use cases (flash, turbo, multilingual, expressive). No explicit when-not-to-use, but the coverage is thorough for a voice tool.

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