click_cell

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

No annotations exist, so the description carries the burden. It discloses the re-identification behavior but omits details like error handling, prerequisite grid state, or click side effects. Minimal but adequate for a simple click action.

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 short sentence that contains all essential information—action and key behavioral trait. No filler, front-loaded, and efficient.

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?

Given the simple one-parameter tool and no output schema, the description covers the core behavior but lacks context about prerequisites, error scenarios, or comparison with click alternatives. Adequate but not full.

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 parameter 'ref' has a minimal schema description ('cell reference'), and the tool description adds no additional meaning about its format or allowed values. Schema coverage is 100% but the description does not enhance understanding.

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 identifies a cell position and clicks it, and specifies it re-identifies the grid each time, distinguishing it from siblings like quick_click_cell. This is a specific verb-resource pair with a behavioral nuance.

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 implies usage when grid re-identification is needed (vs. siblings like quick_click_cell), but it does not explicitly state when to use or avoid this tool. No direct when/when-not guidance is provided.

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