browser_attribute

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

With no annotations, the description carries the transparency burden. The read-only verb 'Get' and the Returns line disclose the operation and response envelope, but the description does not address what happens when the selector matches no element or the attribute is missing, nor does it explicitly guarantee no side effects.

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 compact and well-structured: a one-sentence purpose, a focused Args block, and a Returns line. Every sentence earns its place and the most important information is front-loaded.

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?

The essential invocation details and return shape are present, which is enough for a simple getter. Still, with no annotations, the lack of failure behavior and selector-match ambiguity leaves some contextual gaps for an agent deciding among the many sibling browser tools.

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?

All three parameters are defined beyond the bare schema: serialno is sourced from list_devices, selector is identified as a CSS selector, and attribute includes an href example. This fully compensates for the 0% schema description coverage.

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 opens with a specific verb and resource: 'Get one attribute of an element.' This clearly distinguishes it from sibling browser tools such as browser_text, browser_exists, and browser_state, and the argument descriptions reinforce that it reads a single CSS-selected attribute.

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 purpose sentence implies the tool should be used when a single attribute value is needed, and 'from list_devices' gives a prerequisite for serialno. However, it never explicitly states when not to use it or how to choose between browser_attribute and alternatives like browser_text or browser_execute.

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