audio

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

Annotations indicate non-destructive and non-readOnly behavior, but the description adds no further behavioral details. It does not disclose side effects, authorization needs, or error handling. With no additional transparency beyond annotations, score is low.

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?

Description is concise at two sentences, but the second sentence essentially defers documentation to the help tool. It could be restructured to present key actions first.

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?

Despite having 10 parameters and 4 distinct actions, the description provides only a high-level overview. It lacks explanations of action behaviors, parameter combinations, or return values. Reliance on help tool indicates incomplete self-description.

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?

Input schema covers all 10 parameters with descriptions, so description adds no parameter semantics. Baseline of 3 is appropriate as schema does the heavy lifting.

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?

Clearly states the tool manages audio buses and streams, listing four actions. This distinguishes it from sibling tools which cover other domains like animation or config. However, it doesn't differentiate between the actions themselves within the description.

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. The description simply lists actions and directs user to help for full docs, providing no context on appropriate usage or prerequisites.

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