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

Annotations cover read-only and open-world behavior, so the bar is lower, yet the description still adds real value: real-browser rendering, PNG byte output, and a per-call price of $0.0045 USDC via x402. Pricing is critical behavioral context for an agent choosing among paid tools. It omits rate limits, size limits, and failure behavior for non-public URLs.

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 short sentences, each earning its place: what it produces, how it renders, what it costs. The critical capability and the cost are both front-loaded.

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 does say output is PNG bytes, and it discloses cost. But for a 4-parameter tool with zero schema documentation, the width/height/fullPage semantics and any URL-access limits are missing, leaving the agent to guess before spending money.

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 description coverage is 0% across four parameters (url, width, height, fullPage), so the description carries the full compensation burden. 'Full-page' loosely implies the fullPage flag and 'PNG' covers format, but width/height, defaults, and viewport/clipping semantics are entirely unexplained.

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: 'Full-page PNG screenshot of any public URL rendered by a real browser.' The rendering mechanism and output format are clear. It doesn't explicitly differentiate itself from the many near-neighbors (browser_start, page_actions, crawl, scrape), so it falls 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?

No when-to-use guidance and no alternatives named. The agent must infer from the name that this is for capturing a visual of a page rather than crawling or scraping it. The 'any public URL' phrase implicitly signals the public-only constraint but no exclusions are stated.

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