upscale_image

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

No annotations are provided, so the description carries full burden. It states the tool creates a task and returns IDs status and URLs but does not disclose that the task is asynchronous, that polling occurs via the wait parameter, or any potential costs or side effects. Important behavioral traits are missing.

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 very brief (one sentence) but misses essential details. It is not well-structured; it front-loads the purpose but omits necessary context about the async workflow and parameters.

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 the tool's complexity (5 parameters, no output schema, no annotations, async behavior), the description is grossly inadequate. It does not explain the task lifecycle, how to obtain the upscaled image, or the meaning of any parameters. The agent would struggle to use this tool correctly.

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 only 40% (2 out of 5 parameters have descriptions). The description adds no parameter information, failing to compensate for undocumented parameters like source_image_url. It does not clarify the role of timeout_ms or poll_interval_ms.

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 verb 'Create', the resource 'Recraft task', and the specific action 'upscale image'. It also mentions the return values. This distinguishes it from sibling tools like remove_background or check_pricing.

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 provides minimal guidance on when to use this tool. It doesn't compare with alternatives or specify prerequisites. For example, it doesn't mention that this is for upscaling images while remove_background is for background removal.

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