puppeteer_click

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention potential side effects like navigation (despite the waitForNavigation parameter), element visibility requirements, or error conditions. The agent cannot infer that clicking may trigger network requests or state changes beyond the stated navigation wait.

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, efficient sentence that conveys the core action and a key requirement. While very concise, it lacks structured information (e.g., separate usage notes), but the brevity is not excessive given the tool's simplicity.

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?

With no output schema and no annotations, the description is incomplete. It does not explain return values (e.g., success boolean, error messages), error handling for invalid selectors or missing sessionId, or what happens when waitForNavigation is true. The minimal information forces reliance on the parameter schema alone.

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?

The input schema covers all three parameters with descriptions, achieving 100% coverage. The description adds value by explaining the purpose of sessionId ('maintain state after navigation'), but does not elaborate on selector usage or waitForNavigation behavior beyond what the schema already states.

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 the context ('on the current page'), distinguishing it from sibling tools like puppeteer_navigate or puppeteer_screenshot. However, it does not explicitly differentiate from puppeteer_evaluate, which could also simulate clicks via JavaScript.

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 mentions the requirement for sessionId 'to maintain state after navigation', but provides no guidance on when to use this tool versus alternatives (e.g., puppeteer_evaluate for programmatic clicks, or puppeteer_navigate for page transitions). No when-not-to-use or exclusion criteria are given.

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