ncloud_delete_multiple_objects

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

Annotations already provide destructiveHint=true and idempotentHint=true, and the description adds the critical safeguard: 'Set confirm=true to execute'. This goes beyond the structured hints, informing the agent that a confirmation flag gates execution. No contradiction with annotations.

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 two sentences, front-loaded with the warning symbol, and contains zero filler. Every word adds value.

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?

Given the annotations cover destructive/idempotent behavior and the schema documents all parameters, the description provides adequate context for a bulk delete tool. It doesn't describe return values, but no output schema exists, and the core safety and usage details are present.

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 covers all three parameters with descriptions, including the confirm parameter's explicit purpose. The description's mention of 'Set confirm=true' reinforces the existing schema documentation but adds no new meaning beyond it. With 100% schema coverage, baseline 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 uses the specific verb 'Delete' with the resource 'multiple objects from an Object Storage bucket' and scopes it 'in a single request'. This clearly distinguishes it from sibling tools like ncloud_delete_object (single object) and ncloud_delete_bucket (whole bucket).

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 phrase 'in a single request' signals the batch deletion use case, and the sibling tools list includes ncloud_delete_object for singular deletes, implying the contrast. However, it does not explicitly state when-not to use it or name alternatives, leaving some inference required.

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