browser_screenshot

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

With no annotations provided, the description bears full responsibility for disclosing behavior. It only says 'Take screenshot' and does not mention what happens to the screenshot (saved to disk?), whether it returns a path or data, any side effects, or environmental dependencies. This is grossly insufficient.

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?

The description is extremely terse, but this is under-specification rather than conciseness. No useful information is front-loaded, and the single sentence carries no substantive content about the tool's behavior or usage.

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 tool with three optional parameters and no annotations or output schema, the description is completely inadequate. An agent cannot determine what the tool does beyond the obvious, nor what inputs are expected or what it returns.

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?

While the schema provides 100% coverage of parameters, the descriptions are vague ('Full page screenshot' as a string is particularly unclear). The tool's description adds zero additional meaning to the parameters, and does not compensate for the schema's ambiguity.

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 simply states 'Take screenshot', which is essentially a direct restatement of the tool name 'browser_screenshot'. It conveys a generic verb and resource but provides no specificity about what kind of screenshot, its scope, or how it differs from the sibling tool 'browser_snapshot'.

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?

There is no guidance on when this tool should be used versus its many siblings (e.g., browser_snapshot, browser_state, browser_trace). No context, no exclusions, no alternatives are mentioned.

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