click_element_offset

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

The description discloses core behavior (click at percentage position) and hints that it is not center. However, it does not mention scrolling, waiting, or the 'humanize' default behavior, which would be valuable given no annotations.

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 concise with one sentence plus examples. It front-loads the purpose. However, it lacks parameter explanations, which would improve structure.

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 5 parameters and no annotations, the description is incomplete. It does not explain how to target an element (ref vs selector), the humanize behavior, or the return value (output schema exists but not described).

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 description fails to explain the five parameters, especially 'ref', 'selector', and 'humanize'. The examples only illustrate x_percent and y_percent values. With 0% schema description coverage, the description should compensate but does not.

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 tool clicks inside an element at a percentage position, not the center. It distinguishes from sibling tools like 'click' (which likely clicks center) and provides examples that illustrate specific use cases.

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 implies when to use (clicking at a specific offset) by stating 'not center' and giving examples. It does not explicitly list alternatives or when not to use, but the context is clear enough.

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