browser_get_attribute

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states the core function and does not mention read-only behavior, side effects, error handling (e.g., missing attribute), or return format. It is unclear whether the tool manipulates the page state or simply reads it.

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, clear sentence without redundant words. It is appropriately sized for the simplicity of the tool, delivering the essential purpose without unnecessary detail.

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 tool is simple and the description is understandable, but it lacks information about the return value and behavior in edge cases (e.g., attribute absent or element not found). Given the absence of an output schema, the description could have added a brief note about what is returned, making it only partially complete.

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 input schema provides 100% coverage of parameter descriptions (selector, attribute, sessionId), so the baseline is 3. The description does not add extra parameter semantics, but the schema already defines each parameter clearly.

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 'Get an attribute value from an element' clearly states the action (get), the resource (attribute value), and the target (element). It distinguishes itself from sibling tools like browser_get_text or browser_get_html, which retrieve different aspects of an element.

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 guidance on when to use this tool versus alternatives such as browser_get_text, browser_get_html, or browser_get_title. There is no mention of appropriate contexts, exclusions, or prerequisites.

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