terminal.mouse_click

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

No annotations provided, but description details SGR-1006 press+release sequences and 1-based coordinate system. Does not cover error conditions or session validity, but adequate for a click 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?

Two sentences, no redundancy. First sentence states action, second adds technical context. Efficient and front-loaded.

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?

Covers key behavioral aspects for the 7 parameters. No output schema, so return values implied. Lacks details on error handling, but sufficient for typical use.

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%, but description adds value by clarifying coordinate system ('(1,1) is top-left') and requiring exact sessionId from terminal.start.

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 tool clicks the mouse at a specific terminal position, using SGR-1006 sequences for TUI programs. It distinguishes from related tools like terminal.keys and terminal.mouse_scroll.

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?

Provides a clear prerequisite: mouse mode must be enabled. Does not explicitly exclude alternatives but gives enough context to infer appropriate use.

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