ncloud_gtm_delete_policy_health_check

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

Annotations already mark destructiveHint and idempotentHint, and the description supplements this with a ⚠️ Destructive warning and the explicit requirement to set confirm=true before execution. It adds operational context beyond the annotations, though it doesn't elaborate on irreversibility or side effects beyond the deletion itself.

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?

A single front-loaded sentence with a warning emoji, the action, the target, and the key safety condition. No filler or repetition; the description is minimal but complete.

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 destructive operation, the description covers the action, target, and confirmation requirement, and annotations supply safety/idempotency context. It doesn't describe the return value, but no output schema exists and delete operations often require no return detail; still, it could mention whether the operation is reversible or what happens to the policy afterward.

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%: policyId is described as 'Policy ID' and confirm as 'Must be true to execute.' The description reiterates the confirm requirement but adds no new semantic detail beyond the schema, so baseline 3 applies.

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: 'Delete health check configuration for a GTM policy.' It names a specific verb and resource, distinguishing it from sibling tools like ncloud_gtm_delete_policy and ncloud_gtm_update_policy_health_check.

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 implies use when deleting a policy's health check configuration and provides the required confirm flag, but it does not explicitly contrast with alternatives or state prerequisites. The 'Set confirm=true to execute' is operational guidance rather than decision guidance for choosing this tool.

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