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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the free/paid result split, the x402 payment path via Apify with no account required, bearer-token auth billed in TidyTools credits, and concrete rate limits (1 per IP per UTC day, 20 AI pool, 20 global). This is exactly the cost/auth/throttling context the annotations cannot carry.

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 purpose, then payments, then scope exclusions, then limits – a sensible order with no filler. It is dense and slightly run-on (pricing/auth/rate-limit clauses stacked in consecutive sentences), but every sentence carries operational information.

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 description tells the agent what to expect back (limited free result plus paid upgrade links), how to unlock full results, what auth is needed, and what the quotas are. For a one-parameter, quota-limited tool this leaves nothing important unstated.

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 coverage is 100% and the single parameter is already documented as 'One public HTTP(S) URL.' The description reinforces the one-URL constraint and adds that it must be a 'public image', which is a modest but genuine addition; baseline 3 applies when the schema does the heavy lifting.

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: 'Compresses one public image', plus the scope ('one public image', 'one url'). It does not explicitly distinguish itself from nearby siblings like resize_image, convert_image or upscale_image, so the agent must infer the difference from names alone.

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?

Explicit exclusions are given: 'Use for one url. Not for batch work or unrestricted monitoring.' That tells the agent when not to call it, though it does not name the sibling alternative (e.g. resize_image) that a batch or resize need should route to.

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