Toggle cacheless mode

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

Annotations already mark this as non-read-only, idempotent, and destructive. The description adds meaningful behavioral context: enabling the mode turns off all caching, and disabling it restores performance benefits. It stops short of describing side effects on live traffic, but the core consequence is clearly disclosed.

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 sentences with no wasted content: action, effect, and usage guidance. There is slight redundancy between 'development (cacheless) mode' and 'turning off all caching,' but the structure is front-loaded and easy to parse.

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 3-parameter toggle with no output schema, the description covers the operation, its effects, and the appropriate usage period. It does not explain return values, but that is not required for correct invocation here, and the safety profile is already carried by annotations.

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 description coverage is 100%, so the parameters are already documented. The description restates the enabled flag behavior but adds nothing about username or domain beyond the schema's minimal descriptions. It provides no extra semantic value beyond what the schema already offers.

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 uses a specific verb and resource: 'Turns development (cacheless) mode on or off, based on the enabled flag.' It clearly identifies the affected resource (caching for the website) and the controlling flag. The term 'development (cacheless) mode' distinguishes this tool from generic cache-related siblings.

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 gives explicit guidance on when to enable the mode ('actively developing, testing changes, debugging issues, or when real-time updates must be visible') and when to disable it ('after finishing development work'). It does not explicitly mention alternative tools, but the usage context is clear and actionable.

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