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

Annotations already declare destructive=true and idempotent=false, and the description adds genuinely new behavioral context: it clears whichever page-cache plugin is installed (six named) plus the object cache, and reports which ones it hit. It also discloses the Elementor CSS rewrite side effect and a Connector version prerequisite (0.9.2+), which annotations cannot convey.

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 core action and the key sibling distinction, and every sentence carries information. It runs long because of the Elementor and plugin-list detail, but nothing is redundant 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?

An output schema exists, so return values needn't be explained, and the description covers the destructive scope, the triggering conditions, the sibling boundary, and the one non-obvious parameter. Nothing needed to call it safely 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 coverage is 0%, so the description must carry the load. It explains elementor_regenerate thoroughly (rebuilds Elementor compiled CSS, rewrites stale http:// URLs to https, version requirement), but site_url — including what an empty default does — is only implied by 'a connected WordPress site' and never specified.

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 ('Purge a connected WordPress site's page cache') and immediately differentiates from the sibling wordpress_set_performance, which only purges LiteSpeed when flipping a speed setting. An agent can distinguish the two 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?

Gives explicit when-to-use conditions (after a widget, option, SEO field or theme-file change) and the reason it's needed (those edits don't trigger a purge, so the cache serves stale content for days). It also names the sibling that auto-purges and under what narrow condition, so the boundary is unambiguous.

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