wwise_preview

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 discloses that playback goes through the 'transport' and that the action can play, stop, or pause, which is useful behavioral context. However, it omits whether this is non-destructive, whether it requires an established Wwise session, whether playback stops automatically, and any side effects on project state.

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 two compact lines with the core purpose front-loaded and args listed after. No filler, though the Args block largely restates parameter names rather than adding narrative.

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 no explanation, and both parameters are covered. What is missing is the operational context an agent needs: the required Wwise connection state and whether preview is transient or affects saved project data.

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 explains object_path as the object to preview and restricts action to play/stop/pause, effectively supplying the enum the schema lacks. It does not define path format (GUID vs. hierarchical path), which keeps it short of a 5.

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 opens with a specific verb (Preview) and resource (Wwise object), and parenthetically enumerates the object types (Event, Sound, Container). It is clearly distinguishable from mutating siblings like wwise_create_object or wwise_set_property, though it does not explicitly contrast itself with read-only siblings such as wwise_query.

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 choose preview over alternatives (e.g., ms_audition, ms_stop_audition, or wwise_query), nor on prerequisites such as an active Wwise connection. The only usage signal is implicit in the word 'preview'.

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