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

Annotations only declare readOnly and openWorld, so the description carries real weight: it discloses the return shape (limited free result plus paid upgrade links), the x402/Apify payment path requiring no account, and precise free-tier limits (1 per IP per UTC day, 20 shared pool, 20 global). None of that is in structured fields.

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?

Purpose is front-loaded, followed by return behavior, payment path, scope exclusions, then limits. Every sentence is on-topic, though the stacked rate-limit clause is dense and could read slightly cleaner.

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 a single-parameter tool with no output schema, the description covers what comes back, payment requirements, and quota constraints. The return value is still somewhat vague (what exactly the 'limited free result' contains), keeping it just short of fully self-contained.

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?

With one parameter at 100% schema coverage, the schema already documents 'One public HTTP(S) URL.' The description reinforces 'one public image'/'one url' but adds no format or constraint detail beyond the schema, so the baseline 3 applies.

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+resource+scope: "Upscales one public image by 2x." The 'one' and '2x' distinguish it cleanly from siblings like resize_image, convert_image, and compress_image, so an agent can route to it without opening another schema.

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?

"Use for one url. Not for batch work or unrestricted monitoring" gives explicit scope and exclusions beyond the obvious. It stops short of naming a sibling alternative for batch/image-resizing cases, so it is clear context rather than a full when/when-not/alternative routing.

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