ncloud_ncs_abort_multipart_upload

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

The description explicitly warns '⚠️ Destructive' and states that all uploaded parts are discarded and the uploadId cannot be reused. It also explains the confirm=true requirement, which is critical behavioral context. The annotation destructiveHint=true is consistent with the description, and the description adds meaningful detail about the irreversibility and the confirmation mechanism.

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 compact and front-loaded with the destructive warning and the core action. Every sentence adds value: the HTTP endpoint, the consequence, the non-reusability, and the confirmation requirement. No filler or 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 destructive operation with no output schema, the description covers the essential context: what it does, what is lost, and how to execute it safely. It could mention prerequisites like needing an in-progress multipart upload, but the uploadId parameter and the reference to ncloud_ncs_create_multipart_upload imply that. The destructive annotation and confirm flag together make the safety profile clear.

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 description coverage is 100%, so the schema already documents all four parameters. The description adds context for the confirm parameter ('Must be true to actually execute the destructive operation') and clarifies that uploadId comes from ncloud_ncs_create_multipart_upload, which adds value beyond the schema. However, most parameter meaning is already in the schema, so a 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 states a specific verb ('Abort'), a specific resource ('multipart upload'), and the exact effect ('discard every uploaded part'). It also includes the HTTP DELETE endpoint, which disambiguates it from sibling tools like ncloud_ncs_complete_multipart_upload or ncloud_ncs_list_multipart_uploads.

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 clearly indicates this is for aborting a multipart upload and that the uploadId cannot be reused afterwards, which implies it should be used when the upload should be discarded rather than completed. It does not explicitly name alternatives like ncloud_ncs_complete_multipart_upload, but the context is clear enough for an agent to select it appropriately.

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