recraft_explore

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

With no annotations, the description carries the full burden, and it discloses several behavioral traits: outputs are diverse, style/color control is coarse, and the result includes image IDs intended for recraft_explore_similar. It could go further on side effects such as count of generated images or cost/rate behavior, but the core behavior is transparent.

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 a single, front-loaded sentence with no filler. The purpose, behavioral boundary, and output hook are each conveyed in a compact, scannable way.

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?

Given no output schema, the description usefully provides the key return-value semantic (image IDs for recraft_explore_similar), and the input schema documents all parameters. It does not spell out how many images are produced, but 'set of images' plus 'diverse results' is sufficient for selecting and invoking the tool.

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 5 parameters. The description adds conceptual context about coarse style/color control but no parameter-level detail beyond the schema, 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?

Description states a specific action ('Generate a set of images') and a clear purpose ('visual exploration and discovery'), with a behavior signature ('diverse results from a prompt') that separates it from focused-generation siblings. It also names the follow-up tool recraft_explore_similar, making the tool's role distinctive.

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 phrase 'no fine-grained style/color control' provides an explicit boundary for when this tool is not appropriate, and 'visual exploration and discovery' gives a clear use-case context. It does not explicitly name which sibling to use when fine-grained control is needed, so the guidance stops just short of full alternative routing.

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