zen_click

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

No annotations are provided, and the description does not detail behavioral traits such as whether the click triggers navigation, requires element visibility, or causes side effects. The agent receives minimal behavioral context.

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 concise sentence that directly states the tool's function. There is no wasted text, and the key information is front-loaded.

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?

For a simple click with one parameter and no output schema, the description covers the essential purpose. However, it lacks details on behavior when the element is not found, timeouts, or potential side effects, which are relevant given the sibling tools involve similar interactions.

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?

With 0% schema description coverage, the description adds critical meaning by specifying that the parameter is a 'CSS selector', which is more informative than the raw schema type 'string'. This sufficiently compensates for the missing schema descriptions.

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?

Clearly states the action ('Click') and the resource ('element by CSS selector'), making the tool's purpose straightforward. However, it does not differentiate from sibling tools like 'zen_fill' or 'zen_select_option', which are distinct but could benefit from explicit 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?

No guidance on when to use this tool versus alternatives such as 'zen_fill' or 'zen_snapshot'. No description of prerequisites, error handling, or explicit conditions for use.

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