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

Annotations declare the safety profile (readOnlyHint=false, openWorldHint=true, idempotentHint=true, destructiveHint=false), so the bar is lower; the description adds the confirmation-gated workflow, which is genuinely non-obvious behavior. It does not spell out that an external scan is performed against the open web, which the annotation implies but the text leaves implicit.

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?

One tightly packed sentence plus a short clause, with the action and its precondition front-loaded. No filler, no redundancy with the title.

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-step, confirmation-gated mutation with no output schema, the description conveys the action and the confirmation gate, and the schema covers the token mechanics. It could be slightly richer about what the refresh actually changes, but nothing essential for correct invocation 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?

Schema description coverage is 100% and both parameters, including the confirmation_token two-step flow, are fully documented in the schema. The description adds no syntax or format 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?

States a specific verb+resource ('scan the website... refresh its technology snapshot') and pins the domain to technology, which cleanly separates it from siblings like refresh_listing_news and refresh_listing_scores. The dashboard-alias ('Refresh tech') reinforces the intent unambiguously.

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 clear context (refreshing one of the user's own listings) and the key precondition ('Requires the user's confirmation'), including the two-step nature. It does not explicitly contrast with refresh_listing_scores/news when a user has multiple refresh options, so it stops short of full when/when-not guidance.

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