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

Goes well beyond the annotations by disclosing the real Chrome rendering engine, the PNG output format, specific failure semantics (400 on bad/private URL, 504 on 30s timeout), a per-call price ($0.01 USDC x402), and the default viewport width. These are operational traits the read-only/idempotent hints cannot convey.

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 usage, options, error codes, and price in tight sentences. Every clause carries information; nothing is padding.

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 screenshot tool with no output schema, the description covers purpose, return format (PNG), usage triggers, parameter defaults, error conditions, and cost. An agent has everything needed to call it correctly and interpret failures.

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 already 100%, but the description still adds the default width of 1280, which the schema does not state, and clarifies 'full=true for the whole page.' That marginal value over the schema justifies above the baseline.

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 ('Render any public web page... return a PNG screenshot'), so the agent knows exactly what it produces. It does not differentiate from siblings like webpage_to_markdown or website_status_check, which overlap on the 'inspect a page' use case, so it stops short of a 5.

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?

Provides concrete triggers: 'see how a page looks, check a layout, capture visual evidence, or read content that only appears after JavaScript runs.' It lacks explicit when-not guidance or named alternatives (e.g. use webpage_to_markdown for text extraction), so it is clear context without exclusions.

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