wwise_assign_shareset

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

With no annotations, the description bears the full burden. It mentions the two-step 'plan/apply' approach and that it is undoable, providing some insight into behavior. However, it does not disclose side effects, permissions, or the scope of the operation beyond what is implied.

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 extremely concise, using two sentences to convey purpose and a key behavioral detail. Every word contributes value without redundancy.

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?

Despite conciseness, the description lacks explanation for the required 'mode' parameter and other key inputs. Without output schema or annotations, an agent cannot fully understand how to invoke the tool correctly. The two-step process is mentioned but not detailed, leaving the agent guessing about the workflow.

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?

The description explains that 'reference' should be 'Attenuation' or 'Conversion', adding value beyond the schema which has no descriptions. However, the other four parameters (mode, object_ids, shareset, token) are not explained, leaving significant gaps given 0% schema coverage.

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 clearly states the action ('batch-assign'), the resource ('Attenuation or Conversion ShareSet'), and the target ('objects'). It distinguishes the tool from siblings like wwise_set_properties or wwise_soundbank_assign by specifying the type of shareset and the batch nature.

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 hints at a two-step plan/apply workflow but does not explicitly state when to use this tool versus alternatives like wwise_set_properties. No guidance on prerequisites or exclusion criteria.

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