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

With no annotations, the description carries the full behavioral burden and does so: it discloses plan-based rate/scale limits (5 pages/100 images free, 50/500 Pro), the fact that large sites return a job_id instead of a result, and that the tool returns files rather than mutating the site. Return payload fields (zip_url, replacements, per-image sizes/download URLs) are spelled out.

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-loaded with the primary action and scope, then progressively adds output format, application workflow, and limits. Dense and generally earning its length, though the opening sentence is a long run-on and the deployment recipe could be trimmed.

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?

No output schema exists, so the description must describe return values — and it does, naming the report contents, zip_url, and replacements mapping. Combined with the async job_id path and plan limits, an agent has everything needed to call and handle this tool.

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%, so the baseline is 3; the description adds real context by quantifying the plan caps that determine the default max_pages value. It says nothing about the quality parameter beyond what the schema documents, so it is not a 5.

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 chain (crawl → discover images → convert to WebP) and the exact resource (all images on a public site), with the output artifact named. It is clearly distinguishable from siblings such as convert_image (single file) and list_website_assets (listing only).

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?

Explains the use case concretely (start at one page, follow same-host links) and gives the downstream workflow for applying results to a codebase, plus the async escape hatch via get_website_report. It lacks explicit 'when not to use' or named alternatives, so it stops short of a 5.

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