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

Annotations already declare readOnly=false, destructive=false, openWorld=false, so safety is partly covered; the description adds real behavioral context beyond that, namely the downstream consequence (Blawgy re-checks rankings two weeks later) and the accepted-refresh precondition. The 'safe to call twice' phrasing sits in mild tension with idempotentHint=false, but it asserts safety rather than identical effects, so it is not a hard contradiction.

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 short sentences, each earning its place: the action, the downstream effect, and the precondition plus repeat-safety. The core action is front-loaded and nothing is padded.

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 two-parameter mutation with full schema coverage and no output schema, the description supplies the gating rule and the consequence of calling it, which is what an agent needs. It omits error behavior for a non-accepted refresh, a minor gap given annotations already carry the safety profile.

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%, with both 'site' and 'refreshId' documented in the schema itself. The description's mention of 'the page in a refresh' adds no format or sourcing detail beyond what the schema already provides, so the baseline 3 applies.

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 verb and resource: it marks a page refresh as done and notifies Blawgy that the page was updated. This clearly separates it from request_refresh or get_refresh_brief, though it does not explicitly name any sibling tool to sharpen the distinction.

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?

'Only for an accepted refresh' is a concrete gating condition that tells the agent when the tool is valid, and 'Safe to call twice' covers repeat invocation. It stops short of naming what to use instead when the refresh is not accepted, so it is clear context without explicit alternatives.

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