Clear Website Cache

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Clear cache' without explaining the scope (e.g., entire website vs. specific cache), side effects, or dependencies (e.g., whether cache must be enabled). This is a significant gap for a mutating operation.

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 a single concise sentence, directly front-loaded with the core action and resource. Every word is necessary, and there is no redundancy or filler, making it highly efficient.

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 is minimally sufficient but incomplete given the complexity of the domain. It fails to mention how this relates to hosting accounts, the role of the username/domain, or how it differs from the many sibling cache tools. Without this context, an agent may mis-select this tool.

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 input schema covers 100% of parameters with basic descriptions ('Website domain', 'Hosting account username'). The description adds no additional meaning or relationship between the parameters, so it only meets the baseline without exceeding it.

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 action (clear) and resource (cache for a hosted website), distinguishing it from similar tools like agency_cache_clear and clear_api_cache by the 'hosted website' context. It avoids vague language and directly matches the tool's name.

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?

No guidance is provided on when to use this tool versus alternatives such as hosting_cache_toggle, hosting_cacheless_toggle, or clear_api_cache. The description lacks any conditional use cases, prerequisites, or exclusions, leaving the agent to guess.

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