Randomize controls

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

Discloses that only numeric custom parameters are affected, non-numeric untouched, and explains amount behavior, complementing annotations (readOnlyHint false, destructiveHint false, openWorldHint true) with specific details.

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?

Two brief sentences front-loaded with action and key point, every word adds 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?

Comprehensive for a tool with 4 parameters and no output schema; covers purpose, safety, usage, and pairing with other tools.

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?

Adds meaningful context beyond schema: comp_path as control-panel container, params defaults to all numeric, amount with blend explanation, seed for repeatability.

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?

Clearly states it randomizes numeric custom parameters of a COMP within slider ranges for live improvisation, distinguishing from siblings like manage_presets/manage_cue.

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?

Describes when to use (instant variation for live improvisation) and when not to worry (non-numeric controls left untouched), and suggests pairing with manage_presets/manage_cue.

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