browser_screenshot

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

No annotations provided, but description clearly discloses that the screenshot is discarded unless visual=true, and that it returns an OCR-based text map. Covers key behavior, though could mention that a page must be loaded.

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 sentences, no filler, immediate purpose and parameter explanation. Efficient and well-structured.

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 simple tool (1 optional param, no output schema), the description covers purpose, parameter, and a nuance (screenshot discarding). Lacks explicit mention of prerequisite (page must be navigated).

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?

Only one boolean parameter (visual) with 100% schema coverage. Description mentions the parameter's effect (base64 PNG) and default, adding minimal value beyond the schema's own description.

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 states 'Capture the current page and return an OCR-based text map' – specific verb and resource, and distinguishes from sibling tools like browser_read (DOM reading) and browser_scroll (scrolling).

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 extracting text from rendered page (e.g., images), but no explicit guidance on when to use versus alternatives like browser_read or browser_evaluate for script-controlled content.

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