click_by_text

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

With no annotations, the description must disclose behavioral traits, but it only says 'click element'. It fails to mention whether it waits for the element to be clickable, scrolls into view, handles multiple matches, or uses case-insensitive matching, which are critical for an AI agent.

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 extremely concise at 4 words, but it is under-specified rather than efficiently concise. For a tool with one parameter, it lacks necessary details, making it unhelpful.

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 complexity of browsing automation and the presence of many sibling tools, the description is grossly incomplete. It does not mention return values, error conditions, or behavior with non-existent text, and no output schema is visible to compensate.

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 single parameter 'text' has no description in the schema (0% coverage) and the tool description adds no semantics, such as whether exact match is required or if special characters are supported. This provides minimal guidance beyond the parameter name.

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 'Click element by visible text' clearly states the verb (click) and resource (element by visible text), effectively distinguishing it from siblings like click, click_by_role, and find_by_text.

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?

No guidance is provided on when to use this tool versus alternatives such as click_by_role or find_by_text. There are no usage contexts, prerequisites, or exclusions mentioned.

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