wwise_import_audio

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

With no annotations, the description must carry the full behavioral burden. It does not disclose whether replaceExisting overwrites or destroys existing objects, nor any permission, authentication, or side-effect behavior for the import operation.

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 front-loaded with a one-line purpose and then uses a compact Args section. The example is useful for clarifying the required nested JSON string format and does not feel excessive.

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 mutation/import tool with no annotations, the description still lacks when-to-use guidance and side-effect disclosure, leaving behavioral context incomplete.

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%, but the description compensates substantially: it explains that audio_files is a JSON array of objects with 'audioFile' and 'objectPath' keys, gives a concrete example, lists import_operation values, and notes the language default. It stops short of explaining what each import_operation mode actually does.

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 and resource: 'Import audio files into Wwise.' It is clear what the tool does, though it does not differentiate itself from sibling tools like import_sound_file or wwise_create_object.

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?

No guidance is given on when to use this tool versus alternatives such as import_sound_file, nor when to choose createNew, useExisting, or replaceExisting. The operation values are listed but not explained as usage choices.

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