camofox_click

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

No annotations are provided, so the description must fully disclose behavior. It only says 'Click an element' without mentioning side effects, error states, visibility requirements, or the existence of the 'doubleClick' parameter (which is in the schema). This is insufficient.

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 sentence, making it concise but at the expense of missing critical information. It is not front-loaded with essential details and lacks structure (e.g., parameter explanations). It could be more informative without being verbose.

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 no annotations, no output schema, 6 parameters with low schema coverage, and a complex nested coordinates object, the description is incomplete. It does not explain the doubleClick behavior, required fields, or what the tool returns, leaving the agent with significant gaps.

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 description coverage is only 33%, meaning most parameters (tabId, userId, coordinates, doubleClick) lack descriptions. The tool description only mentions the three targeting methods, omitting required parameters like tabId and userId and the doubleClick option. It does not adequately compensate for the schema gaps.

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 'Click an element' and lists three distinct targeting methods (ref, CSS selector, coordinates), which is a specific verb+resource. It distinguishes from sibling tools like camofox_type (typing) and camofox_press_key (key presses) that have different actions.

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 implies usage for clicking elements but provides no explicit guidance on when to use this tool versus alternatives, or when to choose one targeting method over another. No exclusions or alternative tool mentions are given.

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