Upscale image (Topaz)

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

Annotations indicate a mutation (not read-only). The description discloses credit cost behavior and notes that upscaling returns a URL. It adds useful context beyond annotations without contradiction.

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?

Three concise sentences: purpose, inputs, and result/cost. Information is front-loaded and every sentence adds value with no redundancy.

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?

With 2 parameters and no output schema, the description explains inputs, cost, and return value. It is nearly complete; could optionally mention synchronous behavior but not required.

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 covers both parameters with descriptions. The description adds value by explaining cost implications for upscaleFactor and warning about '8x' usage, providing practical guidance beyond schema.

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 action (upscales), resource (source image), and tool (Topaz). It distinguishes from sibling tools like aetherwave_upscale_video and other image manipulation tools.

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 specifies required inputs (public imageUrl and upscaleFactor) and provides cost guidance based on resolution. It implicitly suggests when to use (upscale an image) but does not explicitly name alternatives or exclusion criteria.

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