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

Annotations declare read-only and open-world behavior. The description adds useful context: real-browser capture, a signed fileUrl per page downloadable without a key for 7 days, and per-page result counting. It still omits rate limits, failure modes, and auth caveats.

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 sentences with no waste: capability, return artifact, and billing unit. It is front-loaded and appropriately sized for an 8-parameter tool.

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, but the description explains the key return artifact and its 7-day signed URL lifetime per page. It leaves advanced capture parameters to the schema and does not describe error or edge behavior, but it is nearly complete for tool selection.

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 75%, and the description only reinforces the format option (PNG/JPEG/PDF). It adds no meaning for delaySec, fullPage, viewport dimensions, waitForSelector, or pdfPageFormat beyond what the schema provides.

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 resources: capture PNG/JPEG screenshots or render PDFs of public web pages in a real browser. The scope is clear enough to distinguish it from sibling data-extraction tools.

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?

Implies usage for public web pages but gives no explicit when-to-use, when-not-to-use, prerequisites, or alternatives. Sibling tools are unrelated, so no routing conflict is addressed.

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