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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the description's real contributions are the reassurance semantics ('nothing is lost; files are fetched from the origin again') and the return contract ('Returns an operation_id'). That the result is an async operation handle resolvable via kinsta_get_operation_status is implied but not stated.

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 compact clauses: operation semantics first, prerequisite second, return value and HTTP endpoint last. No filler, no restatement of the title, and the write intent is front-loaded in caps.

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?

With no output schema, the description takes on the burden of the return contract and does so ('Returns an operation_id'), plus names the upstream lookup tools for both parameters and clarifies the blast radius. An agent has everything needed to call it correctly.

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 both parameters carry their own sourcing descriptions, so the schema does the heavy lifting. The description's mention of cdn_cache_id origin duplicates what cdn_cache_id's schema description already says, adding no format or constraint detail beyond it.

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?

States a specific verb and resource ('clear the CDN cache') with explicit scope ('of one environment'), which is exactly the distinction needed against siblings kinsta_clear_edge_cache and kinsta_clear_site_cache. The verb+scope combination lets an agent disambiguate without opening any schema.

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?

Names the prerequisite chain explicitly: the tool needs cdn_cache_id from kinsta_list_sites, so the agent knows a lookup must precede the call. It does not, however, state when to prefer this over the sibling clear_edge_cache/clear_site_cache tools, leaving the cache-layer choice to inference.

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