browser_take_screenshot

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

No annotations provided, so description carries full burden. It discloses the return value (path to saved screenshot), default filename behavior, and the full_page/element mutual exclusivity. However, it does not mention whether it modifies browser state (e.g., scroll position) or requires any permissions.

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?

Description is a concise docstring with Args and Returns sections. Each parameter gets a brief comment, and the overall structure is clear. Could be slightly more concise, but no unnecessary prose.

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?

With 5 parameters (0 required) and no output schema provided (though flagged as true), the description covers the basic workflow: take screenshot, save to file, return path. Missing details on file overwriting behavior or supported formats for filename extension, but adequate for typical use.

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 has 0% description coverage, so description must compensate. It explains full_page (boolean, cannot combine with element), filename (default template), element (optional description), ref (exact target), and type (enum png/jpeg). More detail on element vs ref disambiguation would be helpful.

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 action: 'Take a screenshot of the current page or element.' It specifies the resource (screenshot) and differentiates between full-page and element captures through parameters. Sibling tools like browser_snapshot might overlap, but the description is specific enough to distinguish.

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?

Description notes that full_page cannot be used with element screenshots, providing a constraint. However, it lacks guidance on when to use this tool versus alternatives like browser_snapshot or browser_resize, and does not mention prerequisites or post-conditions.

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