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

With no annotations, the description carries the full burden of behavioral disclosure. It adds 'browser-based tool' as a useful privacy/processing hint and states the upscaling effect. However, it does not disclose limitations such as file size constraints, output format, or any differences from the non-Pro version.

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 a single concise sentence that packs in the action, result, quality claim, and environment. Every clause adds value, and the parenthetical 'Browser-based tool' is a useful qualifier without being verbose.

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?

Given the tool's simplicity—no input schema, no output schema, no parameters—the description provides the essential information: what it does and that it runs in the browser. It could mention input requirements or output details, but for a no-parameter tool this is reasonably complete.

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 no parameters, so the baseline is 4. The description adds context about the tool's behavior (4x upscaling, AI detail restoration), which is sufficient since there are no parameters to document.

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 function: enlarging images 4x and using AI to restore lost detail. It specifies the resource (images) and the action (upscale), making it distinct from generic image tools, though it does not explicitly contrast with the sibling 'upscaler' tool.

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 no guidance on when to use this tool versus alternatives like 'upscaler' or 'smart-resize'. It only mentions it's browser-based, which hints at an environment but not at usage conditions or exclusions.

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