place_audio_volume

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

No annotations are provided, so the description carries the full burden. It does disclose real behavioral traits: reverb/interior settings activate on player entry, and priority governs precedence when volumes overlap. However, it omits operational context such as whether an editor/UE connection is required, whether the actor persists or is saved, and what the call returns.

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 with the essential verb+resource and purpose, followed by a short usage line and a clean Args list. No filler sentences; only the usage line and the args list could be marginally tighter.

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?

With an output schema present, return values need not be explained, and the parameter semantics are covered in the Args block. What remains missing is environmental preconditions (editor connection, save/persistence behavior), which matters given siblings like ue5_connect and ue5_status.

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 compensate, and it largely does — it defines all five parameters, including non-obvious semantics like 'half-size of the volume box' for extent and 'higher = takes precedence' for priority, plus a default for extent. Minor gap: location units/frame are not specified.

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 ('Place') and resource ('AudioVolume actor'), then immediately defines what that actor is ('defines an ambient audio zone'). This distinguishes it from sibling spawn_audio_emitter and from Wwise-side tools.

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?

Gives concrete usage context — 'Use for rooms, caves, outdoor areas with different acoustic properties' — which tells the agent when this tool applies. It does not name an alternative or state when NOT to use it (e.g., vs. spawn_audio_emitter or template_ambient), so it falls short of 5.

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