Verify a change actually landed on the live page

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

Without annotations, the description must carry transparency, and it does disclose useful error semantics (failed verdict marks response an error) and per-check evaluation. However, it states 'Reloads the URL by default' while the schema sets reload default false and says the default reuses the URL; this contradictory behavioral claim can mislead agents into relying on an automatic fresh reload.

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?

Three sentences are front-loaded with the core purpose, then mechanism/outcome, then motivating use case. No filler; every sentence earns its place.

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?

It covers what the tool does, how it evaluates, and what it returns/error behavior, while the schema fully documents the parameters. The false reload-default statement and absence of any sibling-routing guidance prevent a perfect score, but overall an agent can invoke it correctly.

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 100%, so the schema already documents all five parameters. The description adds general assertion semantics (measured vs expected) but no parameter-level detail beyond that, matching the baseline.

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 observable objective—confirm a fix reached the deployed site rather than a stale local tab—and covers mechanism and output. It clearly separates this verification tool from similar capture/measure siblings.

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?

It gives a clear use case: checking that a fix actually landed and catching stale-local-tab false positives. It does not explicitly name alternatives or when not to use it, so it stops short of a 5.

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