browser_get_by_alt_text

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

There are no annotations, so the description carries the full burden. It gives no details about return behavior, error handling, waiting for elements, or whether the element must exist. This is a minimal factual statement without behavioral context.

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 short, but it is under-specification rather than appropriate conciseness. It essentially restates the tool name and lacks necessary details, so the brevity does not improve understanding.

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?

With 2 parameters, no output schema, and no annotations, the description is inadequate. It does not explain expected return value, behavior with multiple matches, or how 'exact' affects matching. This is insufficient for an agent to invoke the tool confidently.

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%. The description mentions 'alt text' which loosely maps to the 'text' parameter, but does not explain the 'exact' parameter at all. It adds no meaningful insight beyond what the param names already imply.

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 elements by alt text, which is a specific action and resource. It distinguishes itself from sibling tools like get_by_text or get_by_label by mentioning 'alt text'. However, it does not clarify whether it returns a single element, list, or locator.

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 usage guidance is provided. The description does not indicate when to prefer this tool over alternative locator strategies (e.g., get_by_role, get_by_text) or any edge cases for the 'exact' parameter. It only states the basic action.

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