upscale_image

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

With no annotations, the description bears full burden for behavioral disclosure. It mentions returning a task id, status, and output URLs, implying asynchronicity, but lacks details on permissions, cost, side effects, or whether the wait parameter is synchronous. The description is too minimal for a task-creating tool.

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 concise sentence that fronts the purpose. However, it lacks structural elements like sections or examples that could aid clarity, and under-specification may lead to misinterpretation.

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 has 6 parameters (one required), no output schema, and no annotations, the description is insufficient. It doesn't explain the workflow (e.g., how to retrieve results using get_task), parameter usage, or return value format beyond id/status/URLs.

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 low (33%). The description adds no parameter information beyond the schema; it only implicitly references source_image_url via 'output URLs'. It fails to compensate for the undocumented parameters like timeout_ms and 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 tool creates a Topaz task for upscaling images, distinguishing it from the sibling tool 'upscale_video'. The verb 'Create' and resource 'Topaz task' are specific, though the description could elaborate on what 'upscale image' entails.

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?

No explicit guidance on when to use this tool versus siblings like 'upscale_video', 'check_pricing', or 'get_task'. The purpose is implied by the name, but no alternative scoping or prerequisites are provided.

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