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

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=false, openWorldHint=true, destructiveHint=false). The description adds value beyond them: the per-listing rate limit, the dashboard-consistent accuracy/moderation rules, and the mandatory user confirmation. Return/pagination behavior is still unstated.

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?

Front-loaded with the action, then the constraints and the confirmation requirement. Two dense but non-redundant sentences with no filler. Slightly heavy in one sentence structure but every clause 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?

For a non-read-only, non-destructive refresh with no output schema, the description covers purpose, rate limiting, moderation parity, and the confirmation gate. Missing only return-value shape, which is acceptable given there's no output schema.

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 both parameters are already fully documented, including the confirmation_token flow. The description's confirmation note restates what the schema already says and adds no new syntax or format detail. 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?

States a specific verb and resource: 'Look for new coverage of one of the user's approved listings.' An agent can distinguish it from get_news (read existing) and refresh_listing_scores/tech (other refresh targets). It stops short of naming siblings but the action is unambiguous.

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?

Gives concrete usage context, the rate limit ('once a minute per listing') and the confirmation requirement, plus the dashboard parity reference. It doesn't explicitly contrast with get_news, so it falls short of a full when/when-not statement.

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