ncloud_gtm_delete_policy

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

Description highlights the destructive nature, consistent with annotations. Adds context about the confirm safety mechanism, which goes beyond the annotations.

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?

Extremely concise: one short sentence with a warning emoji and clear instruction. No unnecessary 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?

For a simple delete operation with two parameters, the description adequately covers purpose, destructiveness, and the confirm flag. Could mention irreversibility more explicitly but 'permanently delete' suffices.

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%, but description adds important meaning for the 'confirm' parameter (must be true to execute), which is not obvious from schema default alone.

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?

Description clearly states the action (permanently delete) and the resource (Global Traffic Manager policy). It is specific and distinguishes from sibling tools like create/update.

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?

Provides explicit instruction to set confirm=true to execute, but lacks guidance on when to use this tool versus alternatives (e.g., update instead of delete).

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