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

With no annotations, the description carries the full burden. It does usefully disclose the credit cost (3 credits) and that the result is returned as { image }, which is real value. It omits prerequisites, expected latency, whether upscaling is lossless or how the 12 models behave, so the mutation/cost profile is only partly covered.

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 short sentences, front-loaded with the action, followed by return shape and cost. No filler or repeated schema content beyond a brief scale restatement.

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 an 8-parameter image tool with no annotations and no output schema, the description covers what the tool does, what it returns, and what it costs. It leaves out guidance on choosing a Topaz model and on when this beats sibling enhancement tools, which are the main decision points for an agent.

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%, so every parameter already has a description and baseline 3 applies. The description restates only the scale range (1–6x), adding nothing about model selection among the 12 enum options or the interplay of denoise/sharpen/faceEnhancement.

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?

States a specific verb ('Upscale'), resource ('an image'), the backing engine (Topaz Gigapixel AI) and a 1–6x range. It is clear what the tool does, but it never distinguishes itself from near-siblings like enhance_image or ai_expand.

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 scale range implies the use case (enlargement rather than stylistic enhancement), but there is no explicit when-to-use or when-not-to-use guidance and no named alternative for tasks that overlap with enhance_image or ai_expand.

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