skill_click_element

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

The description 'Guide for clicking' contradicts the annotations, which mark the tool as readOnlyHint: true and idempotentHint: true. A click typically modifies state, but annotations declare no side effects. This inconsistency misleads the agent.

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 extremely short (6 words), which is concise but lacks structure. It is not a full sentence and omits critical information, making it insufficient for agent understanding.

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 lack of an output schema and the presence of many sibling tools, the description fails to explain the tool's role. It only mentions it is a guide, leaving the agent unaware of what the tool actually does or returns.

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 tool has zero parameters and 100% schema description coverage. With no parameters, the baseline is 4; the description does not need to add parameter semantics.

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 'Guide for clicking with pikvm_mouse_click' is vague and does not clearly state the tool's function. The name implies an action (click element), but the description suggests it is a guide, causing confusion and failing to distinguish from sibling tools like pikvm_mouse_click.

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 alternatives. Sibling tools such as skill_click_ui_element_workflow or pikvm_mouse_click exist, but there is no comparison or context for selection.

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