ncloud_list_parts

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

Annotations declare readOnlyHint=true, which aligns with the listing behavior. The description adds that it applies to 'in progress' multipart uploads, which is useful but not extensive. No additional behavioral details (e.g., pagination, required state) are disclosed 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 with no unnecessary words. It is front-loaded with the key action. However, it could be slightly more informative without adding length, e.g., mentioning that uploadId must come from initiate_multipart_upload.

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?

No output schema is provided, and the description does not mention the return format (e.g., a list of parts with part number, ETag, size). For a listing tool, this omission hinders an agent's ability to use the output. Also, it does not state that the upload must be initiated first via ncloud_initiate_multipart_upload.

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?

All three parameters (bucketName, objectName, uploadId) have descriptions in the schema (100% coverage). The description does not add any meaning beyond the schema, so baseline score 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 verb (List), resource (uploaded parts), and context (for a multipart upload in progress). It distinguishes from sibling tools like ncloud_list_multipart_uploads (lists uploads, not parts) and ncloud_complete_multipart_upload (completes, not lists).

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 does not explicitly mention when to use this tool versus alternatives (e.g., ncloud_list_multipart_uploads, ncloud_upload_part). It implies usage by stating what it does, but lacks guidance on prerequisites or exclusions.

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