ncloud_edge_purge

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

Annotations already declare idempotentHint=true and destructiveHint=true, so the description's mention of 'cache purge' aligns without contradiction. The description adds context about what is purged (content) and the scopes, but does not disclose additional behaviors like response format or concurrency limits. With annotations covering key traits, the description provides adequate but not high additional value.

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?

Single sentence, front-loaded with verb and resource, no fluff. Every part is necessary and contributes to understanding.

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 tool's simplicity (3 parameters, full schema coverage, no output schema, and annotations present), the description explains the purpose and core options adequately. It does not mention return values, but that is acceptable for a straightforward action like purge. Minor room for improvement (e.g., noting that purge results are tracked via history), but overall complete.

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 every parameter already has a descriptive summary in the schema (e.g., enum values for purgeType, target format). The description merely restates the purge types without adding new meaning or usage notes beyond the schema. Baseline score 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 ('run a cache purge/invalidation'), the resource ('Global Edge CDN edge'), and the supported purge scopes (all, directory, pattern, URL). It is distinct from sibling edge tools (e.g., create, delete, start, stop) which handle lifecycle operations.

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 (e.g., other edge tools). No prerequisites, exclusions, or scenarios provided. The description only lists purge types, not usage context.

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