click_element

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the execution environment (real Chrome via extension, user's browser) which is useful, but says nothing about what clicking causes — navigation, page waits, permissions, or whether the action is reversible.

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 terse components: a bracketed environment/usage caveat followed by the action statement. It is front-loaded and wastes no words, though the bracketed note is somewhat dense compared to the bare action phrase.

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 3-parameter mutation tool with no annotations and no output schema, the description covers the environment and a usage boundary but leaves behavioral effects and expected outcomes unstated. It is minimally adequate rather than 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% and all three parameters are documented in the schema, including the xpath fallback rationale and intent. The description adds no parameter detail beyond the index name already in the schema, so baseline 3 applies.

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 resource (element), and the bracketed preamble identifies the environment as a real Chrome browser via the OctoLimb extension. It distinguishes the tool from recipe-based siblings by contrast, though it does not name a specific alternative like run_recipe.

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?

"use only when the task requires acting on a real website" gives an explicit when-to-use constraint that implicitly steers the agent away from the recipe tools. It stops short of naming the alternative or stating prerequisites, so it's clear but not exhaustive.

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