session_click

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

Annotations provide no read/destructive hints, so the description carries the behavioral burden. It states the action ('Click') but does not disclose that clicking may trigger navigation, state changes, or other side effects, nor does it mention any preconditions beyond the index source.

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?

A single, concise sentence that front-loads the action and the required indexing context. Every word earns its place, with no filler or repetition of schema details.

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 simple two-parameter action with full schema coverage, the description provides enough to invoke the tool correctly. The main gap is the lack of side-effect disclosure, but given the tool's simplicity, the overall context is reasonably 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?

Schema description coverage is 100%, so the schema already documents both parameters. The description adds only the context that the index comes from session_state output, which is also reflected in the schema property description. No significant extra meaning is added.

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 uses a specific verb ('Click') and resource ('interactive element'), and uniquely identifies the mechanism ('by its index (from session_state output)'). This clearly separates it from the generic sibling 'click' and other session tools.

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 phrase 'from session_state output' implies the correct usage pattern: first call session_state, then use the returned index. However, it does not explicitly address when to prefer this over the sibling 'click' tool or when not to use it.

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