Clear website cache

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

Beyond the annotations, the description reveals three important behaviors: the cache clear is permanent, it clears all server-side cache at once, and it conditionally purges Hostinger CDN cache when CDN is enabled. It also adds the WordPress-subdirectory edge case. This is valuable behavioral context that annotations alone do not provide.

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 description is front-loaded with the core action, followed by use cases and edge-case behavior. Every sentence adds distinct information: permanent scope, when to use, CDN behavior, and directory usage. There is no wasted text.

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?

The description covers what the tool does, when to use it, what additional cache it affects, and how to target a subdirectory installation. Combined with complete schema descriptions and annotations, an agent has everything needed to invoke the tool 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 coverage is 100%, and the description adds meaningful behavior for the directory parameter by explaining the WordPress-subdirectory use case. It does not add much to username or domain, but the schema already names those parameters clearly enough. Overall the description enriches parameter understanding beyond the schema.

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 first sentence names the exact operation and scope: 'Permanently clears all server-side cache for the website at once.' It adds CDN-cache behavior, which clearly distinguishes this broad cache-clearing tool from narrower siblings like hosting_purgeLiteSpeedCacheV1. The verb, resource, and scope are specific and unambiguous.

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 explicitly states when to use the tool: 'when content was updated and needs to be visible immediately, or after making major changes.' It does not name alternatives or when-not-to-use cases, so it falls short of full 5-level guidance, but the context is clearly framed.

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