browser_region_screenshot

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

With no annotations, the description must fully disclose behavioral traits. It mentions 'explicitly shared tab' but does not state whether the operation is read-only, what the output format is, or any side effects. The description is too sparse to provide adequate transparency.

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 a single sentence, making it concise. However, it is under-specified for the complexity of the tool (6 parameters, no schema descriptions). The brevity sacrifices necessary detail.

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?

Given the high parameter count, lack of output schema, and many sibling tools, the description is far from complete. It does not explain the coordinate system, the meaning of 'explicitly shared tab', the quality parameter, or the return value. The agent would have insufficient context to use the tool correctly.

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 0%, meaning the schema provides no parameter descriptions. The tool description does not explain any parameters (x, y, width, height, quality, collaboration_id). The phrase 'bounded document region' weakly implies the meaning of coordinates and dimensions, but it is insufficient to guide proper parameter usage.

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 action 'Capture one bounded document region from an explicitly shared tab', using a specific verb and resource. It implicitly distinguishes from sibling tools like browser_screenshot or browser_full_page_screenshot by specifying 'bounded document region', but it does not explicitly name alternatives.

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?

No guidance is provided on when to use this tool versus alternatives like browser_screenshot or browser_full_page_screenshot. It does not mention prerequisites (e.g., tab must be shared) or scenarios where this tool is not appropriate.

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