screenshot

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

Discloses key behaviors: removes banners/ads by default, returns rendered image, and explains all parameters. No annotations provided, so description carries full burden. Lacks mention of rate limits or auth, but fine for screenshot.

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?

Concise description with purpose statement, behavioral note, and structured argument list. No redundant information.

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?

Covers all aspects: purpose, default behaviors, parameter details, and return type. No output schema, but description adequately describes output. No missing context for this tool.

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?

All 6 parameters explained with defaults and usage context. Adds meaning beyond schema (e.g., 'Capture entire scrollable page'). Schema coverage 0% but description compensates fully.

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?

Description clearly states verb 'capture', resource 'screenshot of a web page', and purpose 'for AI/vision use'. It distinguishes from sibling 'extract' by specifying it returns an image.

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?

Implied usage for visual capture vs data extraction. Notes that cookie banners, ads, etc. are removed by default, helping agents understand when to use. Lacks explicit alternatives or exclusions.

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