ncloud_delete_integration

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

The description adds value beyond annotations by explicitly warning 'Destructive' and requiring 'confirm=true' to execute. Annotations already indicate destructiveHint, but the description provides the confirmation mechanism, which is critical for safe usage.

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, using two short sentences and an emoji. Every word serves a purpose, and the key information is front-loaded.

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?

The description is adequate for a simple delete operation, but lacks information about the response or post-deletion state. Since there is no output schema, the description could be more complete by explaining what happens after deletion.

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?

With 100% schema description coverage, the description adds little beyond the schema. It does emphasize the confirm parameter's role in execution, but does not add new meaning for integrationId. Baseline score of 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 explicitly states 'Delete a Cloud Insight integration,' which is a specific verb and resource. It distinguishes from sibling tools like create, update, list, and get by clearly indicating the delete action.

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 provides a clear guideline: 'Set confirm=true to execute,' which prevents accidental deletion. While it does not explicitly state when not to use this tool, the context of sibling tools makes it clear that this is for deletion only.

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