browser_captcha_screenshot

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

No annotations provided; the description adds behavioral context like auto-refresh on small size, but lacks details on side effects, prerequisites, or error behavior. Missing what happens if no captcha found.

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 concise sentences front-loading the main purpose. No redundancy, but could be slightly more structured with parameter grouping.

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 basic usage and output format (PNG), but no explanation of return value (e.g., file path or base64). Missing error conditions and integration with sibling tools.

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 are documented in the schema (100% coverage). The description adds context about auto-detection vs manual selector but does not significantly enhance understanding beyond the schema.

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?

The description clearly states the tool captures a screenshot of a captcha area and saves it as PNG. It mentions auto-detection vs manual selector, distinguishing it from related tools like browser_captcha_detect and browser_captcha_read.

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?

The description implies usage for captcha capture with auto or manual selection, but does not explicitly compare to alternatives like browser_screenshot_element or state when not to use this tool.

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