ncloud_edge_delete_edge

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

Annotations already provide destructiveHint=true and idempotentHint=true. The description adds value by explicitly stating 'Permanently delete', the Stopped status prerequisite, and the confirm safeguard. This goes beyond the annotation hints. However, it does not disclose what happens after deletion (e.g., immediate success, async behavior) or any side effects beyond destruction.

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 extremely concise with only two sentences. It uses a clear warning emoji and front-loads the critical information ('Destructive'). Every sentence is necessary and valuable. No wasted words.

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 low complexity and that annotations cover destructive/idempotent behavior, the description covers the main operational requirements. However, since there is no output schema, the description should at least hint at what the return value indicates (e.g., success/error). The lack of return behavior information leaves a small gap.

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?

Both parameters (edgeId, confirm) have full schema descriptions (100% coverage). The description restates the confirm requirement but adds no new information beyond the schema. Baseline score of 3 is appropriate since the schema already does the heavy lifting.

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 'Permanently delete a Global Edge CDN edge' with a specific verb and resource. It also includes a prerequisite condition (Stopped status) and a necessary flag (confirm=true), which distinguishes this delete operation from other edge-related tools like start or stop.

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 mentions the prerequisite that the edge must be in Stopped status and that confirm must be true to execute. However, it does not provide guidance on when to use this tool versus alternatives (e.g., stopping the edge first) or when not to use it. It lacks explicit exclusions or comparisons to sibling tools.

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