Randomize controls

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

Annotations declare readOnlyHint=false and destructiveHint=false. Description adds that only numeric custom parameters are affected, others are untouched, and the tool is 'always safe to fire', providing useful behavioral context beyond annotations.

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?

Three sentences, front-loaded with main purpose. Every sentence adds value: tool action, parameter behavior, safety, and suggested pairing. No unnecessary words.

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?

No output schema needed for this side-effect tool. Description covers all relevant aspects: what it does (randomize numeric params), how (amount control), safety (ignores non-numeric), and complementary tools. Complete for its complexity.

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 100% with descriptions for all 4 parameters. The description adds extra context: explains amount blending, defaults for params, and typical comp_path usage, enhancing meaning 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?

Clearly states it randomizes a COMP's numeric custom parameters within their slider ranges, providing a specific verb and resource. Distinguishes from siblings by emphasizing safety and improvisation.

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?

Explains the amount parameter controls blend, notes non-numeric controls are untouched ensuring safe use, and suggests pairing with manage_presets/manage_cue. Lacks explicit 'when not to use' but provides strong context.

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