recraft_batch_generate

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

With no annotations provided, the description carries the behavioral disclosure burden. It does well by revealing that generation is sequential, that failure is isolated per asset, and that there is a built-in 300ms rate limit delay. It could mention output/return behavior, but the disclosed pipeline and failure semantics are valuable.

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 with no filler. The core purpose is front-loaded, and the failure-isolation and rate-limit details are presented efficiently.

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?

For a batch tool with nested parameters but no output schema, the description covers the essential behavioral context: sequencing, background removal, saving, failure isolation, and rate limiting. It is complete enough for correct invocation; only a more explicit return/status description would round it out.

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 100%, so the schema already documents all asset properties such as name, prompt, output_dir, remove_bg, and negative_prompt. The description adds high-level pipeline context but not deeper parameter-level meaning, so the baseline score of 3 is appropriate.

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 a specific action ('Generate multiple assets in sequence') and identifies the full pipeline (generate → bg remove → save). This distinguishes it from singular generation sibling tools like recraft_generate_asset and recraft_generate_image.

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 makes the primary usage context explicit: use this tool when generating multiple assets in a single batch. It does not explicitly name alternatives or give exclusion criteria, but the 'multiple assets' framing provides clear context without being vague.

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