regenerate

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

Given no annotations, the description effectively discloses key behaviors: default seed randomization ('Seeds are re-randomized by default') and how overrides apply ('applied to any node input matching the key name'). It lacks mention of potential side effects like queuing costs or resource consumption.

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 extremely concise—two sentences with no wasted words. It front-loads the primary purpose and uses the second sentence to detail overrides and seed behavior, maintaining clarity throughout.

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 main workflow (re-enqueue with overrides) but does not describe what the tool returns (e.g., job ID, status). Given no output schema, this information would be helpful for an agent to process the response.

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 adds practical context beyond the schema: explains overrides as a map of input-name to value, lists common keys (cfg, steps, etc.), and clarifies the interaction between disable_random_seed and seed overrides. This supplements the 100% schema coverage well.

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's action ('Re-enqueue the workflow that produced an existing asset') and distinguishes it from siblings like generate_image or enqueue_workflow by focusing on regeneration from an existing asset.

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 regenerating assets with optional overrides but does not explicitly state when to use this tool versus alternatives like enqueue_workflow or generate_image. No exclusion criteria or comparative guidance is provided.

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