ncloud_sourcedeploy_delete_scenario

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

Annotations already provide destructiveHint=true. The description adds the critical safety mechanism ('Set confirm=true to execute'), which goes beyond annotations. It also includes a warning emoji, making the destructive behavior explicit.

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 a single sentence with the warning front-loaded. Every word serves a purpose: warning, action, and execution condition. No redundancy.

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 does not cover return values or post-deletion state (e.g., success confirmation), and lacks context about irreversibility beyond the warning. For a destructive tool with no output schema, more context about outcomes would improve completeness.

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% with all parameters described. The description adds no new meaning beyond the schema, as the confirm parameter's purpose is already stated in the schema. Baseline 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 clearly states 'Delete a deployment scenario', which is a specific verb-resource pair. It distinguishes itself from sibling tools like ncloud_sourcedeploy_get_scenario and ncloud_sourcedeploy_create_scenario by specifying the destructive action and target resource.

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 no guidance on when to use this tool versus alternatives. It only warns of destructiveness and the need for confirm=true, but does not suggest preconditions like verifying the scenario exists or mention when not to use it.

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