Create macro control

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

The description adds behavioral context about remapping and response curves, but does not detail side effects, error conditions, or the creation process beyond what annotations already indicate (non-destructive write).

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 two sentences, front-loaded with the main action, and every word adds 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?

The description covers the tool's behavior and parameters well, but lacks mention of the return value or output, which is not provided in an output schema.

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 the conceptual purpose of targets' min/max and curve, adding meaningful context beyond the schema descriptions, which already cover all parameters.

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 tool creates a macro knob that drives multiple parameters with remapping, using specific verbs and distinguishing it from sibling tools like create_modulators or create_control_panel.

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 usage for creating a single fader controlling multiple parameters, but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives despite many sibling tools.

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