ncloud_delete_maintenance

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

Annotations provide destructiveHint=true and idempotentHint=true. The description adds the significance of the confirm parameter for actual execution, which is beyond annotation. However, it does not detail what happens upon deletion or any irreversible consequences beyond the destructive label.

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: two effective sentences (including the warning emoji line). Every word adds value. 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?

For a simple destructive operation, the description covers the essential behavior but lacks information about return values (no output schema) and prerequisites (e.g., whether the maintenance must be in a certain state). It is adequate but not comprehensive.

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% for both parameters. The description adds value by explaining that confirm must be set to true to actually execute the delete, which is not obvious from the schema alone. No additional detail on maintenanceId.

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 identifies the tool as deleting a planned maintenance schedule, with a clear verb ('Delete') and resource ('planned maintenance schedule'). The name also matches. Distinguishes from siblings like ncloud_list_maintenances and ncloud_create_maintenance.

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 states 'Set confirm=true to execute' which provides a condition for use, but does not explain when to prefer this tool over alternatives (e.g., update instead of delete) or any prerequisites.

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