wwise_set_reference

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

No annotations are provided, so the description must carry the full behavioral burden. It signals that this is a mutation ('Set a reference'), but does not disclose side effects, whether existing references are overwritten, required permissions or connection state, idempotency, or error conditions. These are significant gaps for a write operation.

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 short and front-loads the purpose before listing arguments. The Args section is compact and each line earns its place, with no redundant prose.

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?

Although an output schema exists, the description is incomplete for a mutation tool with no annotations and many sibling tools. It lacks usage routing, behavioral caveats, permissions, and connection prerequisites, so an agent cannot confidently choose or safely invoke it over related tools like wwise_set_property or wwise_assign_switch.

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 explain the parameters. It does so for all three: object_path (Object path or GUID), reference (Reference name with examples), and value (Target object path or GUID). This substantially compensates for the empty schema, though it could be more precise about path/GUID formats.

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 states a specific verb and resource: 'Set a reference on a Wwise object', and names concrete reference types (OutputBus, Attenuation, SwitchGroupOrStateGroup). This is clearer than a tautology, but it does not explicitly distinguish this operation from siblings like wwise_set_property, wwise_assign_switch, or wwise_set_attenuation.

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 guidance on when to use this tool versus alternatives such as wwise_set_property, wwise_assign_switch, or wwise_set_attenuation. The description only states what the tool does, leaving usage context to inference.

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