wwise_connect

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It states the connection mechanism and default URL but omits whether the connection persists, what authentication is required, what happens on failure, or whether repeated calls are idempotent.

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 brief, front-loaded, and wastes no words. The purpose comes first, followed only by necessary argument detail.

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. However, for a connection tool with no annotations and no schema parameter descriptions, the definition should mention prerequisites, persistence, or relationship to other Wwise tools. It is minimally viable but leaves important context unstated.

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?

With schema description coverage at 0% and one parameter, the description compensates by explaining that url is a WebSocket URL and giving a default value. This adds useful meaning beyond the bare schema, though the schema's empty default string slightly conflicts with the stated default.

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: 'Connect to Wwise via WAAPI.' It is clearly distinguishable from sibling operations like wwise_query or wwise_save. However, it does not explicitly differentiate when this connection tool is needed versus using execute_waapi directly.

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 gives the URL parameter and its default, but provides no guidance on when to use this tool, whether it must be called before other Wwise tools, or what alternatives exist. The agent must infer all usage context.

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