ncloud_ncs_delete_objects

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

Annotations already provide destructiveHint and idempotentHint. The description adds value by stating 'Permanently delete' and the need for confirm=true, reinforcing the destructive nature beyond the structured data.

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 with a warning emoji and a critical instruction. Every word serves a purpose, and it is front-loaded with the warning.

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 with no output schema, the description covers the essential: what it does, that it is destructive, and the confirmation requirement. Return values and error conditions are not critical here.

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 clear descriptions for all parameters. The description does not add new information about parameters but reinforces the confirm parameter's role, which is already described in the schema.

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 verb 'delete', the resource 'multiple objects from a Ncloud Storage bucket', and the required condition 'Set confirm=true to execute'. It distinguishes from singular delete tools (e.g., ncloud_delete_object).

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 explicitly instructs users to set confirm=true to execute the operation, which is critical for a destructive action. However, it does not differentiate from the similar sibling tool ncloud_delete_multiple_objects, missing a chance to guide selection.

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