hosting_clearWebsiteCacheV1

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

With no annotations, the description explains the permanent cache clearing and CDN cache purge. It adds value by detailing the WordPress subdirectory case, though it omits auth and rate limit info.

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 concise sentences: purpose, when to use, and a special case for WordPress subdirectory. No wasted words, front-loaded with key action.

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 simple cache-clearing tool without output schema, the description covers the main action, CDN effect, and a special case. Lacks mention of irreversibility or timing, but sufficient for the task.

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%, so baseline is 3. The description adds meaning to the 'directory' parameter by explaining its use for WordPress subdirectories, improving beyond schema alone.

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 the tool permanently clears all server-side cache for a website, differentiating it from cache-related siblings like disable/enable cache tools. It also mentions CDN cache purging when enabled.

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?

Provides explicit when-to-use scenarios: after content updates or major changes. Lacks explicit when-not or alternatives but gives clear context for usage.

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