assert_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. It only restates the operation and omits critical behavior such as whether a mismatch throws an error or returns a boolean, whether it waits or retries, and how exact matching or timeout affect the result.

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 sentence with no fluff and is easy to read. However, it is terse to the point of under-specification, omitting behavior and guidance that the six-parameter schema and sibling toolset require.

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 6 parameters, 3 required, 0% schema description coverage, no output schema, and no annotations, a one-line description is far from complete. The agent is left to guess failure behavior, return format, selector strategy, exact-matching semantics, timeout handling, and how this assertion differs from the many sibling assertion 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?

Schema description coverage is 0%, so the description must compensate by explaining parameters, but it does not. It gives no meaning for selector, attribute, expected, by, exact, or timeout, and it only vaguely echoes 'expected value' without clarifying how the parameters interact.

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 a specific verification action: it asserts that an element's attribute has the expected value. This clearly distinguishes it from get_attribute (retrieval) and from assert_text/assert_title (other assertion targets), though it doesn't name alternatives explicitly.

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?

There is no guidance about when to use this tool versus get_attribute, assert_text, or other assertion siblings. The phrasing implies it is for verification, but it never explains selection criteria or when an assertion is preferable to a retrieval.

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