click_at_corner

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

With no annotations, the description carries the burden of explaining the action, and it does say this performs a click at an element corner rather than the centre. However, it does not disclose details such as how coordinates are computed, whether the element is scrolled into view, or what happens if the element cannot be found.

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, front-loaded sentence with no wasted words. It conveys the action, the target location, and the typical use case efficiently.

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 there are no annotations, no output schema, low schema coverage, and many sibling click-related tools, this description is not complete enough. An agent still lacks guidance on required fields, whether `ref` or `selector` must be used, return behavior, and how this differs from tools like `click_element_offset` or `humanize_click`.

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 low, with only `offset` having a schema description. The tool description does not explain how to specify the target element via `ref` or `selector`, nor does it clarify the relationship between `corner`, `offset`, and the click position. It adds purpose-level context but fails to compensate for the undocumented parameters.

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 a specific action ('Click a corner of an element') and immediately clarifies the intended use case with close/X buttons, delete icons, and dismiss controls. It explicitly contrasts with centre clicks, which distinguishes it from the sibling `click` tool and other click variants.

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 clear context about when this tool is appropriate: clicking corner-positioned controls like close buttons and dismiss icons. It does not explicitly name alternatives or state when not to use it, so it falls just short of full guidance.

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