screenshot_element

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

The description only says 'take a screenshot' with no behavioral details such as whether it scrolls to the element, waits for loading, or handles errors. Annotations are absent, so the description should carry more weight but fails to disclose traits.

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 very concise (one sentence), but it lacks structure such as bullet points or sections. While not verbose, the brevity sacrifices helpfulness. A better structure would include parameter explanations.

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 tool has 2 parameters (one required), no annotations, an output schema (not described), and many sibling tools, the description is inadequate. It does not explain how to use the parameters or what the output is, leaving the agent with insufficient context.

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?

With 0% schema description coverage, the description should compensate by explaining parameters. It does not: 'selector' and 'path' are left undefined. The description adds no value beyond the parameter names in the schema.

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 states the verb 'take a screenshot' and the resource 'a specific element', which distinguishes it from the sibling 'screenshot' tool that likely captures the entire page. However, it does not explicitly mention that the element is identified by a CSS selector or XPath, leaving some ambiguity.

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 'screenshot' or when not to use it. The description lacks any context about prerequisites or preferred scenarios.

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