ie_click

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

With no annotations, the description should disclose behaviors. It mentions auto-waiting and selector strategies, but omits side effects (e.g., navigation, state changes), error handling, or return behavior, leaving gaps for a critical interaction 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?

The description is extremely concise with two front-loaded sentences, no extraneous words, and directly addresses the primary purpose and key parameters.

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 6 parameters, no output schema, and no annotations, the description leaves significant gaps: it does not explain how to combine 'by' and 'value', the role of 'frame', or the effect of 'wait' and 'timeout', which are necessary for correct invocation.

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 coverage is only 17%, and the description adds meaning for 'by' (listing selector types) and 'action' (listing click/double/right), but does not explain 'value', 'wait', 'frame', or 'timeout', which are crucial for correct usage.

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 an element' and specifies it auto-waits, but it does not explicitly differentiate from sibling tools like ie_hover or ie_press_key, though it mentions action variants (double, right) which provide some distinction.

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 does not provide guidance on when to use this tool versus alternatives (e.g., ie_hover, ie_fill) or any prerequisites, leaving the agent without decision context beyond the basic purpose.

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