creative_mutate

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

No annotations are provided, so the description bears the full disclosure burden. It conveys mutation semantics (substantial, non-cosmetic change with preserved properties) and negative scope, which is valuable, but is silent on determinism via seed, batch behavior (count, parallel_chains), trace output, and language handling — all relevant for an 8-parameter generation tool.

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 short sentences, front-loaded with the core behavior and followed by the usage condition. Efficient, though the closing exclusion could arguably be folded into the usage sentence.

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?

An output schema exists so return values needn't be described, but with 8 parameters at 0% coverage and no annotations, the definition leaves critical operational parameters unexplained. An agent could not predict the effect of count, parallel_chains, seed, or include_trace from this description.

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% across 8 parameters, so the description must compensate and largely does not. Its phrase 'retaining explicitly requested properties' hints at the 'preserve' parameter, but seed, count, language, constraints, include_trace, and parallel_chains are left entirely undefined.

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: 'create substantially different variants while retaining explicitly requested properties.' It distinguishes itself from 'cosmetic rewrites,' which is useful, but never differentiates from the sibling tools creative_generate/expand/cross, so an agent cannot tell which variant-producing tool to pick from purpose alone.

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?

Gives a clear when-to-use condition ('an existing proposal should change in mechanism or expression') plus an explicit exclusion ('not intended to rank or select variants'). Missing is any reference to the alternatives (creative_expand, creative_cross) that compete for this use case.

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