Clear CDN Cache

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

Annotations provide openWorldHint, but the description adds minimal behavioral detail beyond stating it clears cache and returns an operation_id. No mention of asynchrony, duration, or side effects, but it does not contradict annotations.

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, efficient sentence with no wasted words. It front-loads the action and result.

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?

While the tool is simple, the description lacks guidance on when to use it and any potential side effects. It states the return value but does not elaborate on the operation_id's usage or tool behavior. With output schema present, the return is documented elsewhere, but the description still feels incomplete for a destructive action.

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% for the single parameter (env_id), which is adequately described in the schema. The description adds no further semantic meaning beyond what the schema provides.

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), resource (CDN cache), and scope (for an environment). It distinguishes from siblings like kinsta.cdn.image-optimization and kinsta.edge-cache.clear which target different resources.

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 on when to use this tool versus alternatives such as kinsta.edge-cache.clear or kinsta.tools.clear-cache. The description fails to provide context for selection among sibling tools.

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