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

Far exceeds the annotations: discloses a 10s/global rate limit, robots.txt and User-Agent behavior, private/internal address refusal, the paid flow, the exact x402 PaymentRequired error shape, the retry mechanism via params._meta['x402/payment'], and that invalid or all-failed calls are never charged. This is exactly the behavioral context an agent needs and annotations alone would not supply.

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?

Purpose is front-loaded and every clause carries information (constraints, pricing, error contract), but the second half is a dense semicolon-joined run-on that could be trimmed or bulleted for faster scanning.

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?

For a paid, network-fetching screenshot tool with no output schema, the description covers capability limits, payment/error semantics, rate limiting, and safety guarantees. An agent has everything needed to call it correctly, including how to handle the payment challenge.

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 goes further by explaining the payment parameter's role ('Prefer params._meta["x402/payment"]', 'Never a private key or seed phrase') and confirming the viewport dimensions tied to the device enum, adding meaning beyond the schema text.

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 ('Screenshot one public web page in a headless browser') plus the output medium ('returned as an image'), which cleanly separates it from text-extraction siblings like page_to_markdown and from url_status_check. An agent can tell what it produces without opening the 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?

Gives clear operating context and exclusions ('Viewport only, no logins or scripts', 'does not get past bot walls', paid-only at $0.01/page), so an agent knows when the tool applies. It does not explicitly name an alternative sibling to use instead, which keeps it 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.