ncloud_delete_maintenance

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

Annotations already mark the tool as destructive and idempotent. The description adds the crucial behavioral requirement that confirm=true must be set to execute, which is not covered by the annotations. The destructive warning is redundant but consistent.

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 concise sentence with a warning prefix, front-loading the destructive nature. Every word contributes to the core meaning, with no unnecessary elaboration.

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 tool with two parameters, full schema coverage, and relevant annotations, the description captures the essential behavior and confirmation requirement. It omits peripheral details like permissions and return values, but those are not critical 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 provides full descriptions for both parameters (100% coverage). The description's mention of confirm=true essentially restates the schema's own description, adding no new semantic meaning beyond what is already structured.

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 planned maintenance schedule from Cloud Insight', using a specific verb and resource. It distinguishes itself from sibling tools like ncloud_create_maintenance, ncloud_update_maintenance, and ncloud_list_maintenances.

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 clear context for when to use the tool (to delete a planned maintenance schedule), and the confirm=true note offers an operational guideline. It does not explicitly mention alternatives or exclusions, but the delete scope is unambiguous.

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