regenerate

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

Discloses key behaviors: re-enqueues workflow, applies overrides globally, seeds re-randomized by default, and reproduction method. No annotations were provided, so description carries full burden; covers important traits.

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 concise sentences: first states primary action, second explains default behavior and caveats. Front-loaded, no fluff.

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?

Covers parameters and behavior well, but lacks output description (no output schema). Agent doesn't know what the tool returns (e.g., job ID). For a tool with sibling 'enqueue_workflow', this is a gap.

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 has 100% coverage with clear descriptions. Description adds value by listing common override keys (cfg, steps, etc.) and explaining interaction between disable_random_seed and overrides.seed, enriching beyond 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?

Description clearly states 'Re-enqueue the workflow that produced an existing asset' – specific verb and resource. Distinguishes from siblings like 'enqueue_workflow' and 'generate_image' by focusing on existing assets with optional overrides.

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?

Provides clear context: use to regenerate assets with overrides, default seed randomization, and how to reproduce original. Lacks explicit comparison to sibling tools or exclusions.

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