get_audio_bus_layout

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

With no annotations provided, the description carries the full transparency burden. 'List' clearly indicates a read-only operation, and the description discloses the exact data returned (volume, routing, flags, effect chain). It does not mention side effects or permissions, but for a list operation this is sufficient.

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 a single, front-loaded sentence that uses an active verb and succinctly enumerates the returned fields. Every word adds value; there is no wasted text.

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?

With no output schema and no annotations, the description adequately communicates the tool's purpose and the substance of its return value. It could be more explicit about the exact output format (e.g., array of bus objects), but for a simple list operation the coverage is good.

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?

The tool has zero parameters, and the input schema is empty, which is fully covered by the schema. The description correctly adds no parameter semantics. The baseline of 4 applies for zero-parameter tools.

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 uses a specific verb ('List') with a clear resource ('every AudioServer bus') and lists the exact data returned (volume, routing, flags, effect chain). This distinguishes it from sibling audio tools like set_audio_bus or add_audio_bus_effect.

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 implies usage: when you need an overview of all audio buses with their settings, this is the tool. However, it does not explicitly mention when not to use it or contrast with alternatives like get_audio_info or set_audio_bus, so the guidance is implicit rather than explicit.

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