agency-hosting_clearWebsiteCacheV1

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It states it clears all cache types for all domains, but does not mention whether it is destructive, how long it takes, if it affects live traffic, or if there are any side effects. The description is brief and lacks important behavioral nuances.

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 two sentences long, front-loaded with the main action, and contains no fluff. It states the primary function and the scope (all domains, preview domain, all cache types) without unnecessary elaboration.

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?

Given the tool's simplicity (one parameter, no output schema), the description is mostly complete. However, it lacks important context such as the effect on performance, whether it is reversible, or typical use cases. Also, the description does not mention that it clears cache for all domains, which might have significant implications for the user. It is adequate but not comprehensive.

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?

The only parameter, website_uid, is described in the schema as 'Agency Plan website UID', which is clear. The description does not add additional meaning beyond what the schema provides, but with 100% schema coverage and one simple parameter, the baseline 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 clearly states it clears cache for all domains of an Agency Plan website, including preview domain, which distinguishes it from similar tools like hosting_toggleWebsiteCacheV1 and hosting_purgeLiteSpeedCacheV1. It specifies the resource (Agency Plan website) and the action (clear cache), but doesn't differentiate between cache types or mention why it's used.

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 implies when to use it (when needing to clear all cache for an Agency Plan website) but does not explicitly state when not to use it or mention alternatives. It also doesn't mention any prerequisites like website_uid validation or that it affects all domains, which could be important for the agent to decide.

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