isolate_audio

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

The description mentions that it returns a task id, status, and output URLs, implying an async task creation. However, with no annotations, it fails to disclose potential side effects, cost implications, or whether the audio data is uploaded. This is insufficient transparency for a tool with no annotations.

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 concise with two sentences, front-loading the purpose and return values. However, it is very brief and could be slightly more detailed while maintaining conciseness.

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 tool has five parameters, no output schema, and no annotations, the description is too sparse. It lacks essential context about how the task is created, what the output URLs contain, and how polling works. A more complete description would cover parameter usage and task lifecycle.

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 40% (descriptions for 'wait' and 'model'), but the tool description adds no parameter information. For a low-coverage schema, the description should compensate, but it does not explain how to use parameters like source_audio_url, timeout_ms, or poll_interval_ms.

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 action ('Create a ElevenLabs task') and the purpose ('isolate audio'), along with return values. It distinguishes from sibling tools focused on speech or text, though it could be more precise about the scope of 'isolate audio'.

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 usage guidelines are provided. There is no indication of when to use this tool versus alternatives like speech_to_text or text_to_speech, nor any prerequisites or when-not-to-use guidance.

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