Verify browser state

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

Annotations already establish that this is read-only, idempotent, and non-destructive, so the safety profile is covered. But the description adds no behavioral detail beyond that, such as whether verification polls, waits, or how failures are reported, leaving a significant gap because there is no output schema.

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 one short, front-loaded sentence with no filler. The phrasing 'element assertion' is slightly awkward, but the definition is appropriately compact.

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 schema is structurally rich (three assertion variants) and there is no output schema, so the description should clarify behavior and return semantics. It does neither, and it does not mention the target_id requirement or relationship to sibling verification 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 for undocumented parameters, but it only summarizes the three assertion categories. It does not explain target_id, or the meaning of fields like operator, state, exact, and ref, which are critical for forming a correct assertion.

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 names a specific action (verify) and the resources involved (URL, text, or element assertion), so an agent can tell what the tool operates on. It does not, however, compare this to sibling tools like open_click_verify or wait_for, which weakens differentiation.

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 on when to use verify versus alternatives such as observe, wait_for, or list_targets. The description gives no context about the intended workflow or exclusion conditions.

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