browser_take_screenshot_element

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

The annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, establishing the safety profile. The description adds the behavioral detail that the screenshot is saved to the workspace, which is not covered by annotations. It does not contradict the read-only hint, as saving a local file does not mutate the external browser state.

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, tightly worded sentence that front-loads the core action and destination. It contains no filler, redundancy, or unnecessary qualifiers. Every phrase contributes to understanding the tool's function.

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 simple tool with full schema coverage and clear annotations, the description is adequate. It covers the primary behavior (element screenshot and workspace save) but does not mention what the tool returns (e.g., file path) since no output schema exists. This is a minor gap; the overall information provided by description, schema, and annotations is sufficient for an agent to invoke it 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?

The schema has 100% parameter description coverage, with each of the three parameters (type, target, filename) fully explained. The description itself adds no extra parameter-level detail, but given the schema's thoroughness, the baseline of 3 is appropriate. No need for the description to repeat what the schema already provides.

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 that the tool takes a screenshot of a specific element and saves it to the workspace. This distinctive verb+resource phrasing sets it apart from the sibling browser_take_screenshot, which presumably captures the full page. The purpose is immediately obvious and unambiguous.

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 does not explicitly mention when to use this tool versus alternatives, such as browser_take_screenshot for full-page captures. No when-not conditions or alternative tool references are provided. Usage is implied by the name and description, but an agent must infer the distinction without direct guidance.

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