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

readOnlyHint=true already covers the safety profile, so the description's job is added context, and it delivers: the full priority algorithm, the fact that it spans all sites, and what the response contains (site, item with agentText, why it was picked, report progress). It doesn't mention whether the 'why' is machine- or human-readable, but that is minor given annotation coverage.

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?

Two sentences, zero waste: the first front-loads the purpose and the priority ordering, the second lists the return payload. Every clause carries information an agent would otherwise have to guess.

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 no parameters and no output schema, the description must carry both selection logic and return shape, and it does both explicitly. Nothing an agent needs in order to call this correctly is missing.

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?

Zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly implies no filtering or scope arguments are needed.

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 and resource ('the single most important thing to do next') and immediately scopes it ('across all your sites'), which distinguishes it from the sibling list-style tool get_actions. The priority ladder makes the selection semantics concrete rather than vague.

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 ordered ladder (watched site broke → must-fix open → new wording open → done-item recheck → anything else) tells the agent exactly what this tool will prioritize, and it names recheck_page as the follow-up for the confirmed-done case. It stops short of an explicit 'use this instead of get_actions when you want one item rather than a list' exclusion.

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