execute_waapi

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 says execution is 'direct' but does not disclose side effects, required permissions, whether the call can mutate or destroy Wwise state, or error-handling behavior — all important for an arbitrary-execution escape hatch.

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 purpose is front-loaded in a single sentence, followed by a compact bullet list of parameters. Every element is relevant and there is no filler, though the argument list is minimal rather than rich.

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, and the three parameters are at least named. However, for a powerful arbitrary WAAPI execution tool with no annotations and 0% schema coverage, the description lacks critical safety, permission, and usage context.

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. It names all three parameters and gives a concrete URI example ('ak.wwise.core.object.getTypes'), but args_json and options_json are only described generically as 'JSON string of arguments/options' with no format or schema detail.

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 clear verb and resource: 'Execute any WAAPI call directly (escape hatch).' The 'escape hatch' framing distinguishes it from the many specific wwise_* sibling tools, though it does not explicitly name an alternative. An agent can tell this is the generic low-level path rather than a specialized operation.

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 phrase 'escape hatch' implies the tool is for cases not covered by specialized siblings, which is useful implied guidance. However, it does not explicitly state when to prefer this tool over siblings like wwise_query or wwise_set_property, nor does it list exclusions or prerequisites.

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