ncloud_delete_init_scripts

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

Annotations already mark this as destructive and idempotent, but the description adds critical context: the operation is permanent, supports multiple scripts, and requires confirm=true to execute. This goes beyond the structured fields by explaining the confirmation mechanism and the irreversibility.

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, well-structured sentence that front-loads the destructive warning and clearly states the action and the confirmation requirement. Every word earns its place with no repetition or filler.

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 two-parameter delete tool with no output schema, the description plus schema fully cover the essentials: what the tool does, the confirmation flag, and the input list. The destructive warning adds important safety context. Some might expect a note about return values or error cases, but given the low complexity, this is sufficiently complete.

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 both parameters (initScriptNoList and confirm) having descriptions. The description itself adds no additional parameter information beyond what the schema provides, so the 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 the action with a specific verb ('delete') and resource ('init scripts'), and specifies 'permanently' and 'one or more', making the scope explicit. It distinguishes this from other init script tools like list, get, and create.

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 implies usage by stating the action, but does not explicitly mention when to use this tool versus alternatives or any prerequisites (e.g., obtaining script numbers from list_init_scripts). No exclusions are provided, but the context is clear enough for a simple delete operation.

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