hosting_disableWebsiteCacheV1

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

Discloses performance impact and reversible nature. States it does nothing if already disabled. No annotations provided, but description covers key behavioral aspects. Missing details on potential side effects like cache clearing.

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 short, focused sentences. First tells what and warns of impact. Second gives usage guidance and idempotency. 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?

Given simple toggle action, two required params, and no output schema, description sufficiently covers purpose, usage context, and behavior. Alternative is mentioned, making it complete.

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?

Parameter descriptions in schema are minimal. Description does not add further explanation for domain or username. Schema coverage is 100%, so 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?

Clearly states the action (turn off server-side caching) and its effect (until re-enabled). Distinguishes from sibling tools like hosting_enableCachelessModeV1 and hosting_enableWebsiteCacheV1.

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?

Explicitly advises when to use (cache-related issues) and when to prefer an alternative (cacheless mode for dev/debugging). Also notes idempotency (does nothing if already disabled).

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