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

Annotations only declare readOnly=false, destructive=false, openWorld=true; the description adds substantial context beyond that: three distinct outcome states, that "nicht feststellbar" is NOT an all-clear (WordPress may not be starting, stale content may still be served), that content is not lost, that subsequent requests are briefly slower, and that a verified=false response is not a success signal. This is rich, non-obvious behavioral disclosure.

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?

The core action is front-loaded, but the description is dense and meandering, with several em-dash asides ("live gemessen, wirkt nachweislich", "dann war nichts zu leeren") that dilute the message. Much of the content is valuable, but it could be structured more tightly.

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?

No output schema exists, yet the description compensates by describing the three return outcomes and the semantics of a verified=false response, which is exactly what an agent needs for a mutation tool. Combined with the annotation safety profile, nothing critical 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%, so the enum values for scope and the meaning of site_url are already documented in the schema. The description adds that scope can also purge the object cache (Valkey), but this is largely duplicative of the enum descriptions, so the baseline of 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 names a specific verb and resource (clears the WordPress cache of a domain, via the real WP-CLI call "wp litespeed-purge") and states the scope of what is affected. An agent can distinguish it from sibling tools like start_performance_scan or diagnose_website without opening the 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?

"Erster Schritt, wenn Änderungen an der Website nicht sichtbar werden" gives an explicit triggering condition, and the optional scope usage is clarified. However, no alternative sibling tool is named for the case where cache clearing is not the right move (e.g. diagnosing the site instead), so guidance is clear but not fully comparative.

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