recraft_download_image

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

With no annotations, the description carries the behavioral burden; it does state the main side effect (writing to a local file). However, it does not disclose whether existing files are overwritten, whether directories need to exist, or how download failures are surfaced.

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 with no filler; the core action and the practical use case are both front-loaded. Every sentence earns its place.

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 simple two-parameter utility with fully described schema, the description covers what the tool does and when it is useful. It could be more complete by mentioning overwrite behavior or return value, but nothing essential is missing for selection and basic invocation.

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 coverage is 100% and the schema already explains both parameters ('URL to download' and 'local file path to save the image'). The description does not add extra parameter-level meaning beyond restating these roles.

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 names a specific action (download) and resource (image from URL) plus the concrete outcome (saving to a local file). Among siblings, which are all generation/editing tools, this is clearly the only download-and-save utility, so it distinguishes itself.

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?

'Useful for saving generated images' provides a clear context for when to call this tool. It does not name alternatives or exclusions, but no sibling performs the same function, so the absence of explicit when-not guidance is acceptable.

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