session_click

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

No annotations are provided, so the description carries the full burden. It does disclose the session_start requirement and that it returns text after the click, which is useful. However, it does not disclose possible side effects of the click itself, such as navigation, page reloads, form submission, or any destructive consequences, which is a significant gap for a mutation-like tool.

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 well-structured and front-loaded with the core action, followed by return behavior and clear WHEN/NOT WHEN guidance. It is slightly redundant in that 'requires session_start' is restated in the 'no session' exclusion, but overall every sentence earns its place.

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?

For a click tool with no annotations and no schema descriptions, this covers the essential invocation context: session precondition, targeting strategies, return value, and alternatives. It is incomplete only in minor operational details like max_chars semantics and post-click behavior such as waiting for navigation, so it falls short of fully complete.

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 has 0% description coverage, so the description must compensate. It does explain the meaning of selector, target_text, and ref, but it does not mention max_chars, and it does not explain behavior when multiple targeting parameters are provided at once. This is only partial compensation for the missing schema descriptions.

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 action ('click') on a specific resource ('live session page') and enumerates three targeting modes: CSS selector, link text, and snapshot ref. It explicitly differentiates the tool from browser_click and snapshot in the 'WHEN/NOT WHEN' block, so an agent can distinguish it from siblings without opening schemas.

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 explicitly says when to use the tool ('click on an element of an already open page, session alive') and when not to use it: no session → session_start first, one-time open-click-read → browser_click, need element list → snapshot. This is clear alternative routing with named sibling tools.

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