spraay_compute_tts

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

Discloses cost range ($0.03-$0.05 USDC) and references Replicate TTS models, but does not describe output format, latency, or idempotency behavior. Annotations already indicate non-read-only, so description adds limited behavioral context.

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?

Three sentences covering purpose, action, and cost. No wasted words, but could be slightly more structured. Front-loaded with the core function.

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?

Lacks information about output format (audio URL or binary?), prerequisites, and how model selection affects results. Despite having an output schema, the description should at least hint at the output nature.

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 100%, with descriptions for text, model, and language. The tool description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 it converts text to speech via Spraay Compute, distinguishing it from speech-to-text and other compute tools. The verb 'convert' and resource 'text-to-speech' are specific.

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?

No guidance on when to use this tool versus alternatives or when not to use it. No mention of model selection context or prerequisites.

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