ncloud_edge_purge

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description is consistent with that, spelling out what can be invalidated (all content, directory, pattern, URLs). It goes beyond the annotations by documenting the return value (a purge request ID) and the follow-up lookup, though it omits auth/permission or rate-limit context.

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 tightly packed sentences, front-loaded with the action, then scope, then return value. No filler or redundancy.

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 correctly discloses the return value (purge request ID) and how to verify it, and the schema fully covers the parameters. It would be fully complete if it mentioned any preconditions such as a required edge state or permissions, but the essentials are present.

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 documents edgeId, purgeType, and purgeTarget (including the enum values). The description's parallel list of purge modes adds only a loose restatement, not new syntax or constraints. Baseline 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?

States a specific verb and resource ('Run a cache purge (invalidation) on a Global Edge CDN edge') and enumerates the supported purge scopes. It also names the companion status tool, so an agent can distinguish it from ncloud_edge_get_purge_request without opening either 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?

Gives clear context for when to use it (purging CDN edge cache) and routes the agent to ncloud_edge_get_purge_request to check the result. It does not, however, state any when-not conditions or alternatives to purging, so it stops short of full usage guidance.

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