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

Adds substantial context beyond the annotations: it discloses that it reads plugin state first, enumerates three distinct outcomes, warns that the "not determinable" outcome is not an all-clear, and states that content is preserved but the next requests are briefly slower. This is exactly the behavioral disclosure a non-destructive mutation tool needs.

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-loads the core action and mechanism, then layers the outcome semantics. Slightly dense and the "live gemessen, wirkt nachweislich" phrasing is mildly promotional, but every sentence carries functional information.

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 output schema, the description compensates by describing the three possible outcomes and the misleading one, plus the side effect on subsequent requests. An agent has enough to call it and interpret the result correctly.

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 in the schema, including the site_url multi-installation caveat. The description mentions the domain context but adds no parameter syntax or format detail beyond the schema, so the baseline 3 holds.

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 (clears the WordPress cache of a domain) and even names the exact mechanism ("wp litespeed-purge"). An agent can immediately distinguish this from cache-adjacent siblings like get_performance_score or update_wordpress_core.

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?

Explicitly frames the trigger condition: "Erster Schritt, wenn Änderungen an der Website nicht sichtbar werden." That is clear when-to-use guidance. It stops short of naming a specific alternative tool or when-not-to-use, so it doesn't reach a 5.

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