get_element_attribute

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

With no annotations, the description must carry the behavioral burden. The verb 'get' makes clear this is a read operation with no side effects, but it does not disclose behavior on missing elements or attributes (e.g., whether it returns null or throws), which is moderately important for an automated agent.

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?

A single, front-loaded sentence with no filler. Every word contributes: the scope ('one'), the action ('get'), the target ('attribute's value'), and the container ('from an element').

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 simple getter with only two string parameters, this is close to minimally viable. However, the lack of annotations and output schema means the agent still needs to infer return value type and error behavior, leaving some important operational ambiguity for tool selection.

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 is the only source of parameter meaning. It maps 'selector' to identifying the element and 'attribute' to the attribute whose value is returned, which adds useful context beyond the raw property names, though it does not explain selector syntax or attribute name conventions.

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?

States a specific verb, resource, and scope: retrieves a single attribute value from a web element. The word 'one' differentiates it from the sibling tool get_element_attributes, so an agent can distinguish them.

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?

Implies usage: use when you need exactly one attribute value of an element. However, it does not explicitly contrast with alternatives like get_element_attributes or explain when not to use it, leaving the agent to infer based on singular/plural wording.

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