tab_screenshot

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

With no annotations, the description alone must disclose behavioral traits, but it only states the action. It does not mention whether the capture is non-destructive, whether it returns an image payload or path, how fullPage/clip interact, or the effect on the tab. The word 'screenshot' weakly implies read-only capture, but substantial behavioral context is missing.

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?

A single front-loaded sentence with zero filler. It conveys the core operation immediately and leaves parameter details to the schema, which is well documented.

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?

The schema covers all parameters, but with no output schema the description should clarify what the tool returns (e.g., a base64 image or a file path) and confirm basic preconditions. For a simple capture tool this is a moderate gap, making it minimally adequate but not fully complete.

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%, so the structured schema already documents targetId, format, quality, clip, and fullPage. The description adds no parameter-level meaning beyond that, so the baseline 3 is appropriate.

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?

States the exact operation (take a screenshot) and the resource (a tab) in one clear sentence. This differentiates it from sibling tools like banner_get_screenshots and navigation/evaluation tools, so an agent immediately knows its role.

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 gives no guidance on when to choose this over alternatives, no prerequisites (e.g., that a targetId must come from tab_list or a tab must be open), and no exclusions. An agent has to infer usage entirely from the name and schema.

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