browser_take_screenshot

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

The annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds a non-obvious behavioral constraint: the screenshot is observational only and cannot serve as a basis for interaction. It does not describe what the tool returns, but it does not contradict the annotations.

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 short sentences: the first states the core purpose, and the second gives a critical usage caveat. There is no filler, and the most important distinction from browser_snapshot is front-loaded.

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 100% schema coverage, annotations covering the read-only/non-destructive nature, and a clear sibling alternative, the description is largely complete for correct selection and invocation. The only minor gap is that, with no output schema, it does not state whether the result is image data, a saved file path, or something else.

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 description coverage is 100%, and parameters such as type, scale, filename, and fullPage are already well documented in the input schema. The description itself adds no meaningful parameter-level detail, so it meets the baseline for fully covered schemas without adding extra value.

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 a specific verb and resource: 'Take a screenshot of the current page.' It also differentiates itself from the sibling browser_snapshot by noting that screenshots cannot be used to drive actions, so an agent can select the correct tool without inspecting schemas.

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 explicitly says when to use the tool (need a screenshot of the current page) and provides a clear exclusion: you cannot perform actions based on the screenshot. It names browser_snapshot as the alternative for action-oriented use, giving the agent direct routing guidance.

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