ncloud_delete_product_schema

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

Annotations already set destructiveHint=true and idempotentHint=true. The description adds the caveat 'Set confirm=true to execute,' which is critical safety information beyond the annotations. No contradictions are present.

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: one sentence plus a prominent warning emoji. It front-loads the critical 'Destructive' warning and the confirmation requirement. 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 straightforward delete operation with no output schema, the description is complete. It covers the action, the destructiveness, and the execution guard. There are no missing aspects given the tool's simplicity.

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?

The input schema has 100% coverage and describes all three parameters (cw_key, confirm, prodName) with types, descriptions, and required status. The description does not add extra semantics beyond the schema. 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 clearly states 'Delete a user-defined custom schema from Cloud Insight.' The title is null but the tool name and description together provide a specific verb (delete) and resource (user-defined custom schema). Among siblings like ncloud_get_product_schema, ncloud_create_custom_schema, and ncloud_update_product_schema, this tool's purpose is distinct and unambiguous.

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 includes a warning about destructiveness and the requirement to set confirm=true to execute. However, it does not explicitly say when to use this tool versus alternatives (e.g., update or disable), nor does it mention any prerequisites. The context is clear but lacks explicit when-not-to-use guidance.

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