Clear CDN Cache

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

The description discloses that the tool returns an operation_id, which hints at asynchronous processing. The only annotation is openWorldHint: true, which signals external side effects, but the description does not elaborate on the destructive nature, reversibility, or any operational caveats. It adds a little value beyond the annotation but not much.

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, tightly written sentence that gets straight to the point. It states the action, the target, and the return value with zero filler, making it ideal for quick comprehension.

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 tool with two well-documented parameters and no output schema, the description is adequate. It covers the core action and the return type. It could mention that the operation is asynchronous and might require polling the operation status, but that is not strictly necessary for a straightforward cache clear.

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%: both env_id and cdn_cache_id have descriptive comments in the schema. The description does not add any additional parameter semantics beyond what the schema already provides, so a 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?

The description clearly states the action: 'Clear the CDN cache for an environment.' It names the specific verb and resource and mentions the return value (operation_id). It does not explicitly differentiate from sibling tools like kinsta_tools_clear-cache or kinsta_edge-cache_clear, but the purpose is unambiguous on its own.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or which scenarios favor this over the similar cache-clearing tools. The description simply states what it does without any usage context.

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