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

Beyond the annotations, the description discloses concrete effects: the Redis slave list cache, the nginx proxy cache (AMP included), and the collection's own article/advertisement lists are all invalidated, plus the publication-state condition that governs the nginx purge. It stops short of stating permissions, whether caches repopulate, or what the response looks like. No contradiction with idempotentHint/destructiveHint.

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 tight sentences, front-loaded with the action and progressively narrowing to the specific caches, with the parameter hint last. No filler, though the parenthetical '(AMP included)' is the only marginally expendable clause.

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 cache-invalidation tool with no output schema, the description covers what is purged and under what condition, which is the information an agent needs to call it safely. The main remaining gap is the absence of usage context relative to sibling purge tools.

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 carries the burden, and it partially does by telling the caller to pass either collection_id or collection_uuid, implying they are alternatives. It gives no format detail for the UUID, no precedence rule if both are supplied, and no clarification given that neither parameter is technically required.

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 ('Clear the cache of a collection') and itemizes exactly which caches are targeted (Redis slave list, nginx proxy, article/advertisement lists), which clearly distinguishes it from page/article/advertisement cache tools. It does not, however, name any sibling alternative explicitly.

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?

There is no explicit when-to-use or when-not-to-use statement, and no routing to the many closely named siblings (clear_article_cache, clear_page_cache, purge_nginx_cache, purge_cache_group). The only conditional given ('once it is published') describes behavior rather than selection guidance.

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