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

Description adds viewport modes and full-page behavior, but with no annotations covering safety, it does not disclose whether it renders JavaScript, waits for network idle, or any rate limits. Adequate but minimal.

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?

Two compact sentences, front-loaded with the core action, no unnecessary detail.

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?

Core function and primary options are covered, but wait_ms and wait_for semantics are missing, and no alternatives are cited. Since output schema is absent, description does not clarify return format, though 'PNG' implies it.

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?

Description explicitly maps viewport enum values to device types and explains full_page mode, compensating for the schema's lack of descriptions. However, wait_ms and wait_for are left undocumented, so not all parameters are clarified.

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?

Clear verb 'Capture' with resource 'webpage', specifies output format PNG. Distinguishes from sibling tools like scrape_webpage and extract_structured_data which imply text/dataset extraction.

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 guidance on when to choose this tool over siblings like scrape_webpage or extract_metadata. Does not mention contexts such as needing visual verification or excluding dynamic pages.

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