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

With annotations (readOnlyHint: false, openWorldHint: true, idempotentHint: false, destructiveHint: false), the agent already knows this mutates data. The description adds no behavioral context such as whether the operation is asynchronous, requires polling, modifies the original, or produces a download URL. The placeholder text 'Before sample:' and 'After sample:' adds no behavioral information.

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 overly long and repetitive, with six near-redundant bullet points about quality enhancement. It also contains unfinished placeholder text ('Before sample:' repeated), which is not useful. The first sentence is informative but the rest could be condensed to one or two lines.

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 tool has an output schema, but the description does not explain what the tool returns, how to handle polling, or any side effects. It also doesn't clarify the difference between src_file_url and src_file_id inputs. For a tool with moderate complexity, the description is incomplete and leaves critical operational questions unanswered.

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 input schema already provides descriptions for 'scale' (values 1, 2, 4) and source file URL/ID. The description does not mention any parameters, but the schema coverage is 50% or effectively high enough that parameters are documented. A baseline of 3 is appropriate because the description adds nothing beyond the 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 tool's core function: 'uses advanced AI and deep learning to analyze image details and improve resolution, making low-resolution images clear & fix motion blur.' Bullet points further enumerate features like 'No More Pixelation' and 'Fix Blurry Photos.' However, it does not explicitly distinguish this tool from siblings such as AI-Photo-Lighting or AI-Photo-Colorize, though the name and core enhancement goal are clear.

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?

There is no guidance on when to use this tool versus alternatives. The description is purely promotional, listing benefits but never stating scenarios (e.g., 'use for low-res or blurry images') or exclusions. No mention of prerequisites like file format or size, nor any comparison to sibling tools like AI-Video-Enhancer.

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