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

Annotations only declare readOnlyHint=false and openWorldHint=true, so the description must carry the rest. It never says whether the call is synchronous or returns a task handle (the presence of nexscope_media_task_result in siblings makes this a real ambiguity), what permissions or credits are consumed, or how long it takes.

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?

One short sentence with no padding and the primary action front-loaded. It is efficient, though its brevity is closer to under-specification than model conciseness.

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 no output schema, the agent is left not knowing whether a URL, base64 payload, or async task ID comes back. For a media generation tool in a large suite where results are often retrieved via a separate task-result tool, that omission is material.

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 100%, including the 4096px limit and the 1-4 magnification range, so the schema does the heavy lifting. The description only gestures at enhanceQuality with 'optionally enhance visual quality' and adds nothing on imageUrl or magnification beyond what is already documented.

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 verb and resource are explicit: increase image resolution, with an optional quality enhancement step. However, it does nothing to distinguish itself from adjacent media tools like nexscope_product_image_enhancement or nexscope_similar_image_variations, so sibling selection still requires guesswork.

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 statement of when to use this versus the many other image tools, no prerequisites, and no exclusions. The word 'optionally' hints at the enhanceQuality toggle but gives no guidance on when to set it.

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