agency-hosting_clearAgencyPlanWebsiteCacheV1

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

With no annotations provided, the description covers the basic behavior: clearing all cache types for all domains. However, it lacks details on side effects, asynchronicity, rate limits, or permissions. Minimal but sufficient for a simple cache 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?

Two concise sentences: first defines the action and scope, second reinforces completeness. No unnecessary words.

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 low-complexity tool with one parameter and no output schema, the description is adequate. It covers what is cleared and for which resource. Missing return value details, but the outcome is implied.

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% with one parameter fully described. The description does not add any additional meaning beyond the schema. No mention of parameter format, constraints, or examples.

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 (clears cache), the resource (Agency Plan website), and the scope (all domains including preview domain, all cache types). It distinguishes from siblings like 'hosting_clearWebsiteCacheV1' by specifying Agency Plan context.

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 use for Agency Plan websites but provides no explicit guidance on when to use this tool versus alternatives (e.g., 'hosting_clearWebsiteCacheV1' for non-Agency Plan sites). No exclusions or prerequisites mentioned.

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