ruyi_dom_click

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Click DOM element,' revealing nothing about side effects, waiting behavior, error conditions, or whether the click is a read-only operation. This is essentially a restatement of the tool name.

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 short and to the point, making it concise. However, it is so underspecified that it borders on a tautology, and there is no structured presentation of additional context that would justify this minimalism.

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?

Without an output schema or annotations, the description is the only source of context, and it lacks essential information such as return values, success/failure behavior, element state requirements, or fallback actions. Given the large number of sibling tools, this level of minimalism is inadequate.

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 input schema describes 'selector' but not 'pageIdx,' giving 50% coverage. The tool description adds no parameter information whatsoever, failing to explain the relationship between the two parameters or compensate for the missing schema description.

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 action (click) and the target (DOM element), giving a specific verb+resource. However, it does not explicitly distinguish itself from sibling tools like ruyi_dom_select or ruyi_human_click, which also involve DOM interactions.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, context, or exclusions, leaving the agent to guess when clicking a DOM element is appropriate.

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