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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so safety is partly covered. The description goes further by disclosing the concrete side effect on state — issues that are fixed become resolved, new findings open — which the annotations do not express. It stops short of returning format, timing or auth details, so it is strong but not exhaustive.

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 tightly packed sentences: action, differentiating scope, then the recommended timing. The behavioral payoff (scores refreshed, issue list settled) is front-loaded and there is no filler.

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 tool with no output schema, the description supplies everything an agent needs: what changes, when to run it, what downstream tool (get_site_health) will reflect the result, and which sibling handles the narrow case. No material gaps remain, especially with idempotent/non-destructive annotations covering the risk 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%, so both parameters are already documented (url: must be on the site's domain, defaults to homepage; site_id). The description adds only the vague phrase "a site's page" and no syntax or format detail beyond the schema, 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 gives a specific compound verb ("Re-crawl and re-analyse") plus the resource (a site's page/site-wide analysis) and immediately names the sibling it differs from ("run_analysis only covers a single URL"). An agent can distinguish refresh_site from run_analysis without opening either schema.

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 states the triggering condition explicitly ("Run it after making fixes so get_site_health reflects them") and names the alternative plus its scope boundary (run_analysis = single URL). Nothing about when to prefer this tool over its sibling is left to inference.

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