remove_audio_bus

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It states the removal action and the index constraint, but does not disclose side effects (e.g., whether removing a bus affects audio routing), irreversibility, or required permissions. For a destructive operation, this is insufficient.

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 one sentence, front-loaded with the action and constraint, and contains no superfluous words. While concise, it sacrifices completeness for brevity.

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?

For a simple removal tool with one parameter and no output schema, the description provides the basic action and constraint. However, it lacks contextual information about the impact on the audio bus layout, potential errors, and relationship to sibling tools, making it minimally adequate.

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% with a single parameter 'index'. The description essentially repeats the schema's minimum constraint and description, adding no new information beyond what is already in the schema. Baseline for high coverage is 3, and no additional value is provided.

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 'Remove' and the resource 'audio bus', with a specific constraint about the Master bus at index 0. It distinguishes from sibling tools like add_audio_bus and set_audio_bus by focusing on removal, but does not explicitly differentiate from other bus-related tools.

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 is provided on when to use this tool versus alternatives like set_audio_bus_volume or add_audio_bus_effect. The description only mentions a limitation (cannot remove Master), but does not clarify the context or prerequisites.

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