polynodes_isomorph_switch

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

Annotations already declare the safety profile (idempotent, not read-only, not destructive), so the bar is lower, but the description adds nothing beyond 'JSON confirmation' - no state persistence, no side effects on the audio graph, no indication of what a toggle does to an in-progress effect.

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?

It is short and front-loaded, which is good, but the 'Args:'/'Returns:' blocks are boilerplate that recite the schema and add no information - borderline waste rather than concise value.

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?

With an output schema present, the return value need not be explained, and the state semantics are covered in the nested schema. Still, for a modulation toggle no context is given about the effect being switched or how it interacts with siblings like isomorph_mod_depth.

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% at the top level, so the description must compensate; instead it merely restates the schema ('params: state') without adding meaning. The actual 0.0=off/1.0=on semantics live in the nested $defs, not in the description, so no value is added here.

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 ('Turn IsoMorph modulation on or off'), which is clear enough to act on. However, it does not differentiate itself from the near-identical sibling polynodes_isomorph_mod_switch, whose name an agent could easily confuse with this one.

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?

There is no guidance on when to toggle this switch versus related siblings, no prerequisites (e.g., whether an IsoMorph effect must be selected first), and no mention of the alternative polynodes_isomorph_mod_switch. Usage must be entirely inferred.

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