ncloud_ncs_list_multipart_uploads

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

The readOnlyHint annotation already signals a safe read operation, and the description adds meaningful context: incomplete uploads keep consuming storage until completed or aborted, and the operation is a GET request. 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?

Two focused sentences: the first front-loads verb, resource, scope, and endpoint; the second adds the operational rationale and follow-up tool. Every sentence earns its place with no 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?

Together with a well-documented schema, the description gives enough to select and invoke the tool: required bucketName, optional filters, pagination markers, and the cleanup rationale. The lack of an output schema is a minor gap, but pagination behavior is already conveyed through the keyMarker and uploadIdMarker parameter descriptions.

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 fully documents all five parameters (100% coverage), including constraints and pagination relationships, so the description does not need to repeat them. The description adds no parameter-specific detail beyond the bucket context.

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?

States a concrete action: list in-progress multipart uploads in a bucket, with explicit scope ('not yet completed or aborted') and the REST path (GET /?uploads). This clearly distinguishes it from multipart siblings like complete, abort, and list_parts.

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?

Explicitly frames when to use the tool: to find leftover uploads consuming storage, and even names the follow-up tool ncloud_ncs_abort_multipart_upload. It does not enumerate when-not-to-use exclusions, but there is no competing tool for listing NCS multipart uploads, so the guidance is sufficient.

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