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

With no annotations, the description carries the full transparency burden. It discloses meaningful behaviors: dispatch to AI workers, variable credit costs, file deletion after processing, auditability, and workspace/credit restrictions. It stops short of explaining the output mechanism, but adds substantial context beyond a simple 'upscale' statement.

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 front-loaded with the purpose and then provides relevant operational/policy details. It is slightly verbose with pricing and workspace information, but every sentence adds useful context for an agent deciding whether and how to use the tool.

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?

The description covers credits, file deletion, and audit trails, but with an empty input schema and no output schema it does not explain how the target image is selected or how the upscaled result is returned. This leaves a notable gap for a no-parameter tool, though the operational details help.

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?

The tool has zero parameters, so the baseline is 4. There are no parameter meanings to clarify, and the description appropriately does not invent any.

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 opens with 'Upscale Image — Enlarge images using AI while preserving quality,' clearly stating the tool's verb and resource. It does not explicitly differentiate from the similarly named sibling mio_ai_upscale_pro, but it is specific enough to convey the core purpose.

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 operational context such as 'AI Studio run' and credit details, but it does not give explicit when-to-use or when-not-to-use guidance, nor does it mention alternative tools like mio_image_resize or mio_ai_upscale_pro. Usage is implied rather than directly stated.

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