Toggle website cache

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

Beyond the annotations, the description discloses the performance impact of disabling caching, the no-op behavior when already in the requested state, and the recommendation context. It aligns with idempotentHint=true and readOnlyHint=false, though it could more directly explain why destructiveHint=true is set, such as whether disabling clears cached data.

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 front-loaded with the core action, then gives rationale, an explicit alternative, and the idempotency guarantee. Each sentence contributes useful information without unnecessary padding.

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 three-parameter tool with full schema coverage, the description provides the key behavioral details an agent needs: what the flag does, when to enable/disable, which alternative to prefer, and the idempotent no-op behavior. No output schema is present, so return-value explanation is not required.

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%, and the enabled parameter is already documented as 'Turn server-side caching on (true) or off (false)'. The description reinforces this by saying the action is 'based on the enabled flag', but adds little new parameter-level meaning beyond usage context already covered by the schema.

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 opens with a specific verb and resource: 'Turns server-side caching for the website on or off, based on the enabled flag.' It clearly differentiates this from related cache tools by naming cacheless mode as a distinct alternative, so an agent can distinguish it from hosting_toggleCachelessModeV1 and hosting_clearWebsiteCacheV1.

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?

It explicitly states when the tool is appropriate ('recommended for production websites') and when it is not ('to temporarily bypass caching while developing or debugging, prefer toggling cacheless mode instead'). This gives an agent a concrete decision rule and names the sibling alternative.

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