Clear website cache

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

Annotations already mark this as destructive, non-read-only, and idempotent. The description adds valuable behavioral detail by specifying that all cache types are cleared and that every associated domain, including the preview domain, is affected. This goes beyond the structured annotations.

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 short and front-loaded, with the core scope stated in the first sentence. The second sentence adds the 'all cache types' detail, though it is slightly redundant with the first sentence's mention of clearing cache.

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 single-parameter destructive cache-clearing tool, the description sufficiently explains what is affected: all domains, the preview domain, and all cache types. No output schema exists, but return-value details are not critical for this operation. The lack of explicit mention of recovery or post-clear behavior is a minor gap.

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%, with website_uid already documented as 'Agency Plan website UID.' The tool description does not need to add parameter detail and does not significantly expand on the schema, so the baseline score of 3 is appropriate.

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 specifies a concrete action ('Clears cache') and a precise resource scope: all domains associated with an Agency Plan website, including its preview domain. This clearly distinguishes it from sibling tools like hosting_clearWebsiteCacheV1 and hosting_toggleWebsiteCacheV1.

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 makes clear that this tool is for Agency Plan websites, which is useful context. However, it does not explicitly state when to use this tool over sibling cache-related tools, nor does it mention any alternatives or exclusions.

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