session_click

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Click' indicates a user-like interaction but does not disclose whether the click can trigger navigation, whether it waits for the page to settle, what happens if the element is not found, or whether it may invalidate a prior snapshot.

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, front-loaded sentence with no wasted words. It immediately identifies the action and the two targeting options, making it easy to scan.

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?

There is no output schema and no annotations, so the description alone must make the tool fully understandable. It omits important operational context, such as tabId's meaning, whether a click waits for navigation, error behavior for invalid selectors, and whether the function returns a new snapshot or just a success indicator.

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 description adds some meaning for selector and ref by introducing 'CSS selector' and '@eN ref from a snapshot,' but the schema already states that ref is used instead of selector. The tabId parameter is completely undocumented in both the schema and the description, and with only 33% schema coverage, the description should compensate more.

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 a specific verb ('Click') and a specific resource ('an element'), and clearly identifies the two targeting methods: CSS selector or @eN ref from a snapshot. This makes the tool's purpose distinct from siblings like session_type or session_press without requiring the schema.

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?

Usage context is implied by the action itself: when you need to click an element, use this tool. However, the description gives no explicit guidance about when to prefer session_click over session_press, session_fill, or session_select, nor when to choose a CSS selector versus a snapshot ref.

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