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

Annotations already declare destructiveHint=true and openWorldHint=true, so the agent knows this mutation affects external state. The description adds useful context, namely that the flush is tied to Elementor visual-change workflows, but it does not disclose scope (whether the whole site or one page is affected) or that forced CSS regeneration is the side effect. The annotation idempotentHint=false is also not explained.

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?

Two short sentences, front-loaded with the action and followed by the trigger condition. No wasted wording.

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 small two-parameter mutation tool with annotations, the description covers purpose and timing adequately. It falls short on the optional post_id scoping question and on the consequences of the destructive cache flush, which an agent would want before calling it.

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 50%: site_id is documented in the schema, but post_id has no description anywhere. The description never mentions post_id or whether the flush is site-wide versus post-scoped, which is the most consequential ambiguity for this tool.

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 ('Flushes Elementor CSS cache'), which distinguishes it from the generic cache-clearing sibling without naming it. It is clear, though it does not explicitly differentiate itself from wp_clear_cache.

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?

The description gives explicit timing guidance: 'Call this after Elementor visual changes so the preview reflects the update.' It states when to use it, but does not state when not to use it or name an alternative for non-Elementor caching.

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