zen_click

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

No annotations provided, so description must disclose behavior. It only states 'Click an element' without explaining error handling (e.g., element not found, coordinates out of bounds), return behavior, or side effects like navigation triggers.

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?

Description is short (5 lines), purpose front-loaded, parameter list follows. No wasted words, though could be slightly more efficient if it merged the purpose with the fallback logic.

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 4 params, no output schema, and no annotations, the description lacks key details: return value, interaction with page lifecycle (does it wait for element?), error scenarios. Insufficient for full understanding.

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?

Description adds meaning beyond schema's minimal titles: explains that x/y are used only if selector is empty, provides CSS selector examples, and clarifies tab_id defaults to active tab. This compensates for 0% schema description coverage.

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?

States verb 'Click' and resource 'element on the page', with two modalities by CSS selector or coordinates. Distinguishes from sibling click-like tools (e.g., double_click, trusted_click) by option of coordinate-based clicking, but doesn't explicitly differentiate from all.

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 explicit guidance on when to use this tool vs alternatives (e.g., double_click, hover) or when not to use it. Lacks prerequisites or context like element visibility requirements.

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