ncloud_gtm_delete_policy

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

Annotations already indicate destructiveHint and idempotentHint. The description adds context beyond these: it clarifies the deletion is 'permanent' and that confirm=true is necessary. This goes beyond the structured annotations and helps the agent understand the irreversible nature and confirmation requirement without relying solely on the annotation flags.

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 and front-loaded with the critical warning. It conveys the action, permanence, and confirmation requirement in one sentence. No filler or redundant content.

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?

For a simple 2-parameter destructive operation with full schema coverage and no output schema, the description is complete. It states the action, permanence, and the confirmation requirement. No additional return-value explanation is needed, and the annotations cover the safety profile.

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% (both policyId and confirm have descriptions). The description reinforces the confirm parameter's role ('Set confirm=true to execute') but doesn't add new parameter-level meaning beyond what the schema already provides. Thus, 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?

The description clearly states the action: 'Permanently delete a Global Traffic Manager policy.' It uses a specific verb (delete) and resource (GTM policy), distinguishing it from sibling tools like create, update, or get. The destructive nature is explicitly flagged.

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 an important usage instruction: 'Set confirm=true to execute.' This implies the tool requires explicit confirmation for the destructive action. However, it doesn't explicitly mention when to use this tool vs alternatives (e.g., checking with get_policy_detail first or using update instead). The guidance is minimal but useful.

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