wwise_bus_stats

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

The description explicitly declares the tool as 'Read-only', which is a key behavioral trait. In the absence of annotations, this disclosure is valuable and sufficient for a simple tool with no side effects. However, no further details on output format or performance implications are provided.

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, efficient sentence with no wasted words. It conveys the essential information in a clear and front-loaded manner.

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 parameterless, read-only tool without an output schema, the description is adequately complete. It states what the tool counts and that it is read-only. Minor improvement could include mentioning the output is a count per bus, but it is not necessary given the simplicity.

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?

Since there are zero parameters and schema description coverage is 100%, the description does not need to add parameter semantics. The description adds context by explaining the purpose, which is beneficial beyond the empty 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 a specific action ('Count') and resource ('objects routing to each Output Bus'), with a clear purpose ('mix-routing overview'). It effectively distinguishes this tool from siblings like wwise_audit or wwise_query by specifying a focused, numeric output.

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 for obtaining a bus routing count but does not explicitly state when to use this tool over alternatives or provide exclusions. No guidance on prerequisites 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.