charlotte_click

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

Without annotations, the description carries the burden. It discloses that after the click the full page representation is returned, which is helpful. However, it does not mention potential side effects like navigation, failure handling, or wait behavior. The behavioral disclosure is adequate but shallow.

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, which is concise and front-loaded. It contains no unnecessary words. However, it could be slightly more structured or informative without losing conciseness.

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 simple tool and no output schema, the description is minimally complete. It covers the action and return value but omits details like waiting for page load, error conditions, or interaction with the page state. For a click tool that may cause navigation, more context is warranted.

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 100%, so baseline is 3. The description adds no extra meaning beyond the schema for any parameter. It does not explain the purpose of element_id, click_type, or modifiers beyond what the schema already provides.

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 states 'Click an interactive element on the page' which clearly indicates the action and resource. However, it does not explicitly differentiate from sibling tools like charlotte_click_at (which likely clicks at coordinates) or charlotte_select, leaving some ambiguity.

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 like charlotte_click_at, charlotte_toggle, or charlotte_type. The agent receives no context for choosing among interaction tools.

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