ecamm_set_volume

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the mutation/safety profile is covered externally. The description adds nothing beyond that — no word on whether the change is immediate, persisted across sessions, or what happens if the named bus is inactive. "0-100" merely restates schema bounds.

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 single short sentence is front-loaded and free of filler, which is good. But it is terse to the point of under-specification rather than efficient — the same character budget could have carried a bus example or a units note.

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 two-required-parameter mutation with no output schema and minimal annotations, the description should explain success/failure behavior and the scope of the bus argument. Neither is present, leaving real gaps for an agent invoking it against a live mixer.

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 0%, so the description must carry parameter meaning, and it largely fails. It repeats the 0-100 range that the schema already enforces via minimum/maximum, and never says what the number represents (percent of full scale? linear gain?) or that `bus` accepts a fixed enumerated set of mixer channels.

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?

"Set a bus volume" is a specific verb plus resource, and the 0-100 range narrows the operation further. It does not, however, distinguish this tool from adjacent siblings such as ecamm_set_mute or ecamm_toggle, which an agent must infer from names alone.

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?

There is no when-to-use guidance, no statement of prerequisites (e.g., the bus must exist or be active), and no pointer to alternatives for muting or audio-routing. The agent is left to guess the operating context entirely.

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