ncloud_list_multipart_uploads

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

Annotations already declare readOnlyHint=true. Description adds that it lists 'in-progress' uploads, providing slight behavioral clarity. However, it does not disclose pagination behavior, response structure, or limits beyond the schema.

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?

Single sentence, concise, and front-loaded with the essential information. No redundant or unnecessary content.

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?

Given high schema coverage and annotations, the description is minimally adequate. However, it lacks any mention of output format (e.g., list of upload IDs, keys, pagination), which could be helpful since there is no output 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?

Schema description coverage is 100%, so the schema already documents all three parameters (prefix, delimiter, bucketName). Description does not add further meaning or examples beyond what the schema provides.

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?

Description states the action ('List') and resource ('in-progress multipart uploads for a bucket') clearly. It distinguishes from sibling tools like ncloud_list_parts (lists parts of a specific upload) and ncloud_initiate_multipart_upload (creates 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?

Description implies usage context (list in-progress multipart uploads per bucket) but does not explicitly state when to use this tool versus alternatives like ncloud_list_objects or ncloud_list_parts. No when-not or exclusion criteria provided.

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