click_at_corner

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

Discloses the corner parameter and offset behavior (inset pixels from corner, default 8px), which is not in the schema. However, it omits error handling behavior (e.g., if element not found) and does not mention any side effects, which would be helpful for a click action tool.

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?

Extremely concise: two lines for purpose and explicit use cases, then two lines for parameter details. Every sentence adds value with no redundancy.

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?

The description covers the core behavior and primary parameters, but lacks explanation for the optional 'ref' and 'selector' parameters. Given that the schema has no descriptions (0% coverage) and no annotations, the description should address all parameters to be fully complete.

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 explains the 'corner' enum and 'offset' integer (with example default). However, it does not document 'ref' and 'selector' parameters, which remain entirely unexplained despite 0% schema description coverage. Only 2 of 4 parameters are clarified.

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?

Description clearly states 'Click at a corner of element' with specific use cases like close X buttons and delete icons. This effectively distinguishes it from sibling tools like 'click' (center click) and 'click_element_offset' (arbitrary offset).

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?

Description implies usage for corner-based interactions (dismiss buttons, delete icons) but does not explicitly state when to use this tool versus alternatives like 'click' or 'click_element_offset'. No exclusions or when-not-to-use guidance provided.

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