wwise_generate_banks

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

No annotations are provided, so the description carries the entire behavioral burden, and it discloses almost nothing. It never says whether banks are overwritten, whether an authoring session must be connected, how long generation takes, or what side effects occur in the project. This is a build/mutation-style operation and the gaps are significant.

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?

Two short lines, with the purpose front-loaded and the parameter detail second. The Args block is slightly boilerplate but wastes no meaningful space.

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, with zero annotation coverage and no behavioral context for a generation/overwrite operation, the description is thinner than an agent would want before invoking it safely.

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 coverage is 0% and the schema only types bank_names as a bare string, so the description does real work: it clarifies the value is a JSON array of bank names and supplies a concrete example of the expected format. This compensates well for the schema gap.

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 (Generate) and resource (Wwise SoundBanks), which cleanly distinguishes it from siblings like wwise_import_audio, wwise_create_event, or wwise_save. No explicit sibling differentiation is given, but the verb+resource pair is unambiguous.

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 no when-to-use guidance, no prerequisites (e.g. Wwise must be connected/authoring session open), and no alternatives among the many wwise_* siblings. The only context is the parameter note, which is not usage guidance.

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