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

Beyond the readOnlyHint/destructiveHint annotations, the description discloses non-obvious traits: the ~48-hour output validity window, that images over 1 MB are described rather than returned inline, and that downloading consumes no extra compression quota. These are exactly the operational facts an agent needs before calling.

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?

Front-loads the action and the source of the input, then packs expiry, return shape, size threshold and quota into a compact block. Dense but every clause carries information; the trailing 'GET /output/{id}' is a useful endpoint anchor rather than filler.

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 and one parameter, the description carries the burden well by describing the returned image and its metadata. The one wrinkle is the >1 MB case, where it says the image is 'described' without specifying what representation the caller actually receives.

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 sole parameter's format, length bounds and 48h note are already documented in the schema. The description restates the 48h validity but adds no new syntax or format detail beyond what the schema provides, 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 and resource ('Fetch the compressed image... and return it as an image') and ties it directly to the sibling that produces the input ('of an earlier tinypng_compress_image'). An agent can distinguish this from tinypng_compress_image and tinypng_transform_image without opening a 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?

Clearly states the condition for use: retrieving the output of a prior compress call via its output_url, within a ~48h window. It does not explicitly contrast against tinypng_transform_image or note what to do when the output has expired, so it falls short of full when/when-not guidance.

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