humanize_click

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

With no annotations, the description must fully disclose behavior. It mentions 'Bezier-curve' and 'randomized dwell' to hint at human-like slow movement, but omits key details like whether it triggers events, works on hidden elements, or has a timeout. This is insufficient for an agent to anticipate side effects.

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 sentence with a star emoji, making it concise and front-loaded. However, it sacrifices clarity and completeness for brevity, earning a middle score.

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 that an output schema exists (not shown) and the tool involves a non-trivial humanized click behavior, the description is inadequate. It fails to cover return values, prerequisites, or the distinction from similar tools, leaving the agent underinformed.

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%, so the description should explain the two parameters (ref and selector). It does not mention them at all, leaving the agent to infer their meaning from common patterns or sibling tools. This is a significant gap.

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 'Click with Bezier-curve mouse approach + randomized dwell', which specifies the action (click) and a distinguishing technique (Bezier curve) that sets it apart from a plain click. However, it does not explicitly mention the target resource, such as 'web element' or 'UI component', 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 the many sibling click variants (e.g., click, click_and_wait, click_at_corner). The description lacks any context about preferred scenarios, limitations, or alternatives.

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