ncloud_list_parts

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

The readOnlyHint annotation already signals this is a safe read operation. The description adds the 'in progress' constraint, which is useful context (the tool only works for active uploads). However, it does not mention potential errors, pagination, or response format, so it adds only marginal behavioral detail beyond the annotation.

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, concise sentence that conveys all necessary information without any wasted words. It is front-loaded with the action and resource.

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 read-only list operation with a 100% schema coverage and no output schema, the description is largely complete. It clearly states the purpose and the condition ('in progress'), though it could have explicitly mentioned that bucketName, objectName, and uploadId identify the specific upload, but this is already evident from the schema.

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 provides complete coverage (100%) with clear descriptions for all three required parameters: bucketName, objectName, and uploadId. The tool description does not add further parameter details, but given the high schema coverage, 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 ('List uploaded parts') and the specific resource ('a multipart upload in progress'), which precisely identifies this tool and differentiates it from sibling tools like ncloud_list_multipart_uploads (which lists uploads, not parts). The verb and resource are unambiguous.

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 progress' implies this tool is used after initiating a multipart upload and after uploading parts, but before completing or aborting. It provides clear context for when to use it, though it does not explicitly name alternative tools or state when not to use it.

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