ncloud_serverless_delete_imported_backup

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description adds value by explicitly warning 'Destructive', requiring confirm=true, noting the 202 async operation, and disclosing the 409 conflict condition. This goes beyond the annotations without contradicting them.

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 compact and front-loaded with the most important warning ('Destructive'), followed by the action, endpoint, and key behavioral notes. Every sentence earns its place; no filler or repetition of schema details.

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 two-parameter destructive tool with no output schema, the description covers the essential context: what it does, the endpoint, the async nature, the conflict condition, and the confirmation requirement. It doesn't explain what the 202 Operation response contains, but that's minor given the absence of an output schema and the simplicity of the operation.

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%, so the schema already documents both parameters. The description adds the critical semantic that confirm must be true to actually execute the destructive operation, which is not fully captured by the schema's default false. This is meaningful added value beyond the schema.

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 states a specific verb ('Delete'), a specific resource ('imported backup'), and the exact API endpoint (DELETE /mysql/v1/imported-backups/{backupName}). It also notes the async 202 Operation response, which distinguishes it from other serverless backup tools like ncloud_serverless_list_imported_backups or ncloud_serverless_create_imported_backup.

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 clearly indicates this is a destructive operation and that confirm=true is required to execute. It also mentions a 409 conflict while a restore is using the backup, which is a useful when-not-to-use signal. However, it doesn't explicitly name alternative tools or state when to prefer them, so it falls just short of a 5.

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