browser_get_by_role

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

No annotations are provided, so the description must cover behavioral traits. It only states the basic function, omitting details like whether it returns the first match, what happens if no element is found, whether it waits for the element, or if it returns a locator handle. This is a significant gap for an interactive browser 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 sentence that is front-loaded and to the point. No wasted words, and it immediately communicates the essential action and criteria.

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 tool with no output schema and no annotations, the description is insufficient for an agent to use it reliably. It lacks usage context, return value expectations, and error behavior. While it names the key parameter, it does not provide enough to distinguish effective use from misuse.

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?

With 0% schema description coverage and only two parameter names ('name' and 'role'), the description adds minimal value. It clarifies that the tool locates by 'role' but does not explain the purpose of the 'name' parameter (e.g., accessible name filter). The description does not compensate for the lack of schema details.

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 '通过角色查找元素' (Find element by role) clearly states a specific action (find element) and a specific method (by role), distinguishing it from sibling tools like browser_get_by_text or browser_get_by_label. It conveys the core purpose without ambiguity.

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 provides no information about when to use this tool instead of alternatives. There is no mention of ARIA roles, accessibility considerations, or comparison with other get_by_* locators, leaving the agent without guidance on tool selection.

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