browser_screenshot_element

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

No annotations are present, so the description must fully disclose behavior. It only states the action without explaining side effects, output format (e.g., base64 vs. saved file), or any special conditions. The description adds no meaningful behavioral context beyond the tool name.

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 short phrase with no redundancy or unnecessary words, making it highly concise. However, it is under-specified, but that is penalized in other dimensions rather than here.

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 no annotations and no output schema, the description must provide enough context to invoke the tool correctly. It fails to mention the path parameter's role, return value, or any nuances about element selection, leaving significant gaps in an agent's ability to use it properly.

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%, and the description does not mention either 'selector' or 'path'. While 'selector' is implied by the tool name, the purpose of 'path' is completely unexplained, leaving a critical gap for the agent to know whether it is for saving to a file or something else.

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 '截取元素截图' translates to 'capture element screenshot', clearly identifying the action of taking a screenshot of a specific element. It names a specific verb and resource, and the tool name itself distinguishes it from the full-page browser_screenshot sibling, though the description does not explicitly draw that distinction.

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 provides no guidance on when to use this tool versus browser_screenshot or other element-based tools. It lacks any mention of prerequisites, alternatives, or typical use cases, leaving the agent without context for selection.

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