game_audio_bus

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

The description indicates a mutating action ('Set'), but provides no details on side effects, persistence, or other behavioral traits. With no annotations like readOnlyHint or destructiveHint, the description fails to disclose sufficient behavioral context.

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?

A single, direct sentence with no unnecessary words. Every part earns its place.

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?

The description is minimal but acceptable for a simple setter tool with no required parameters and no output schema. However, it lacks examples or additional context about default behavior.

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 descriptions cover 100% of parameters, so the description adds minimal meaning. The description merely reiterates schema content (volume, mute, solo) without extra context.

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 verb 'Set' and the resource 'audio bus', and lists the properties (volume, mute, solo) that can be modified. It distinguishes this tool from sibling tools like 'game_audio_bus_layout' and 'game_audio_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?

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites, context, or when not to use it.

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