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

With no annotations, the description carries the full burden and does so: cost ($0.008 USDC), charge-only-on-success semantics, the unpaid failure path (x402 payment requirements returned), and the exact retry channel (_meta["x402/payment"]). It also discloses rendering behavior (JS rendered) and viewport size.

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?

Three compact sentences, each earning its place: what is captured, what it costs and returns, and how to recover from the payment failure. Front-loaded with the capability before price details.

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, yet the description names the return field and encoding, covers payment lifecycle and failure recovery, and specifies the rendering context. Only gaps are timing/timeout behavior and an explicit contrast with screenshot_full.

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?

Single parameter with 100% schema coverage means the schema already defines 'url'; the description adds the constraint that it must be a public http(s) page and names the result field image_base64, which the schema does not.

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 ('Screenshot ... of a public page'), plus the defining scope ('visible part', '1280x800 viewport', 'JavaScript rendered') that tells it apart from screenshot_full and scrape 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?

The qualifier 'visible part' implicitly signals the viewport-only case versus a full-page sibling, and 'public page' excludes authenticated content, but screenshot_full is never named so the agent must infer the routing rule. No explicit when-not guidance.

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