setup_drum_bus

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

The description states it groups tracks into a bus with compression, but does not disclose important behavioral details such as whether original tracks are muted, how routing is set up, or what happens to existing sends. With no annotations provided, the description carries full burden but 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 well-structured with a clear main sentence, an explanatory paragraph, and a parameter list. It is fairly concise, though the Args section could be integrated with the schema descriptions to reduce redundancy.

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 5 parameters and no output schema or annotations, the description explains what the tool does and parameter purposes. However, it lacks information on return values, side effects, or how the bus interacts with existing routing, leaving some gaps for a complete understanding.

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 schema has 0% description coverage, but the description provides meaningful parameter explanations in an Args section (e.g., source_tracks format, typical ranges for glue_threshold_db and glue_ratio). These add significant value beyond the naked schema.

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 tool's purpose: 'Group drum tracks into a dedicated bus with a glue compressor.' It distinguishes itself from sibling tools like setup_parallel_compression by explicitly comparing to a 'lighter-touch version of parallel compression.'

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 provides clear usage context: it is for 'gentle comp gluing' and controlling the drum group's overall level, with an explicit note that it's different from parallel compression. However, it does not explicitly list when not to use it or name specific alternative tools.

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