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

Beyond the annotations (readOnly/idempotent/openWorld), the description discloses concrete operational facts: a $0.01 USDC x402 charge per successful call, a 256KB POST body limit working out to ~190KB input, metadata stripping, EXIF auto-orient, and an alternate HTTPS endpoint. It stops short of describing failure/error behavior or the return payload, so it earns a 4 rather than a 5.

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?

It is dense but front-loaded: capability and limits come first, the request-body example anchors the shape, and pricing/endpoint go last. Every clause carries information an agent needs, and nothing is wasted.

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 input side is complete, including a hard size constraint that would otherwise cause silent failures. However, there is no output schema and the description never says what comes back (base64 bytes, a URL, dimensions), which is a material gap for an image-processing tool an agent must chain on.

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%, so the schema already documents all eight parameters including enum values and defaults. The description restates the same facts (width/height up to 4096, fit modes, formats, quality, auto-orient) without adding new semantics; 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?

The description opens with a specific verb and resource ('Resize / convert an image (GD)') and enumerates the operations supported (dimensions, fit modes, output formats). It is clear what the tool does, but it never distinguishes itself from the sibling `format_convert` or `image_info`, which overlap with the 'convert' and image-inspection territory.

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?

Usage context is implied rather than stated: the size cap and the example body suggest when the tool is viable, but there is no explicit 'use this when you need X, use format_convert/image_info otherwise'. An agent must infer the boundary with the sibling tools.

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