set_wavetable_property

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

No annotations are provided, so the description carries the full burden. It states 'Set' (mutation) but does not disclose potential side effects, reversibility, permission requirements, or behavior on invalid values. For a mutation tool, this is a significant gap.

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 well-structured with a concise purpose, a clear list of writable properties, and a parameter list. It is front-loaded with the core purpose and every sentence adds useful information; no fluff.

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?

The description covers the property names, parameter semantics, and valid values, making it fairly complete for a setter tool. It lacks information about error handling, return values, and side effects, but the output schema (though not shown) likely covers return data. Slight gaps remain.

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%, but the description compensates thoroughly by listing all valid property names and enumerating acceptable values for several (e.g., effect_mode, filter_routing, mono_poly). It also explains the meaning of each parameter, adding substantial value beyond the schema.

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: 'Set a Wavetable property that is not a device parameter.' It specifies the resource (Wavetable property) and distinguishes from set_device_parameter, making it 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 implies when to use by contrasting with device parameters, and lists all writable property names, giving clear context. However, it doesn't explicitly state alternative tools or when NOT to use it, though the distinction is implicit.

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