browser_get_by_text

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

With no annotations, the description carries the full burden, but it only says 'find element by text'. It does not disclose whether matching is exact or substring, case sensitivity, whether it returns the first match or all, or what happens if no element is found. This is a significant gap for a locator 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?

The description is a single short phrase, which is concise, but it lacks sufficient structure and information. It is under-specified rather than properly concise; a few additional sentences could clarify behavior without bloating.

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 lack of annotations and output schema, and the existence of many sibling locator tools, the description is incomplete. It does not explain the return value, the exact parameter semantics, or how this tool differs from get_by_title or get_by_role. An agent would be uncertain when to select this tool and how to use it correctly.

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 0%, so the description must explain the parameters. It only reiterates 'by text', leaving the 'exact' boolean parameter completely unexplained. The agent cannot know what 'exact' controls (e.g., case sensitivity, substring matching) without additional context.

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 the tool finds an element by text, which is a clear verb+resource. However, it does not distinguish from sibling tools like get_by_role, get_by_label, etc., which also locate elements by different criteria.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that it is specifically for text-based lookup or when other locators would be more appropriate. The user must infer usage from the name.

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