template_ui_sound

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the tool creates an ActorMixer, Sound, Event, and bus routing, but it omits prerequisites like whether a Wwise connection is required, whether existing objects are overwritten, and whether the operation is saved automatically.

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?

Front-loaded and compact: one sentence states the purpose and created components, followed by a short Args list. Every line earns its place with no unnecessary filler.

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?

An output schema exists, so return values need not be explained. For a multi-object creation template with no annotations, the description covers enough to invoke but leaves gaps around connection requirements, overwrite behavior, and side effects.

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 supply parameter meaning. It lists both arguments, but the stated bus_path default ('Master Audio Bus') conflicts with the schema default ('') and omits the schema's sound_name default ('Click').

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?

States a specific verb and resource: create a non-spatial UI sound. It names the internal Wwise objects created (ActorMixer(UI) + Sound + Event + bus routing), which makes it clearly distinguishable from generic object/event creation and from other templates like template_footsteps.

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 the context (UI sounds) but does not say when to use this tool versus alternatives such as wwise_create_object, wwise_create_event, or other template tools. No exclusions or prerequisites are given.

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