ncloud_cdnplus_request_purge

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

The description explicitly calls the operation 'purge (invalidation),' which contradicts the annotation destructiveHint=false. This is a clear inconsistency, and the description fails to disclose the destructive nature of the operation beyond the schema. The annotation contradiction undermines trust.

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 concise, with two focused sentences that front-load the core action and scope. Every word contributes to the purpose, making it efficient 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?

Given the 100% schema coverage and lack of output schema, the description is minimally adequate for parameter understanding. However, the contradiction between the description and the destructiveHint annotation creates a significant gap in behavioral context, making it incomplete for safe usage. More explanation of side effects or confirmation steps would be needed.

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 schema already explains parameters. The description adds minimal context by mentioning 'isWholeDomain/isWholePurge select scope,' which marginally clarifies the boolean flags but does not explain relationships between parameters (e.g., domainIdList vs isWholeDomain). This fits the baseline of 3.

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 tool's function: 'Request a CDN+ cache purge (invalidation)' with specific scope options ('whole content or specific files/directory'). It distinguishes from siblings by naming CDN+, differentiating it from Global CDN purge tools.

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 some context (CDN+ purge, whole or specific scope) but does not provide explicit guidance on when to use this tool versus alternatives like ncloud_globalcdn_request_purge. No exclusions or alternative recommendations are mentioned.

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