ncloud_upload_part

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

With no annotations, the description carries the full burden but only restates the operation ('Upload a part') and the workflow. It fails to disclose side effects, permission requirements, idempotency, or state changes. No contradictions with annotations since annotations are empty.

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 sentences, front-loaded with the core operation and including the essential workflow. Every word earns its place with no 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?

The description covers the multipart lifecycle (initiate, upload, complete) and the schema documents all parameters. However, it omits details like part upload ordering, response behavior, or constraints beyond schema, leaving the agent with some ambiguity about invocation expectations.

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 coverage is 100% and each parameter has a description. The tool description adds no meaning beyond the schema; it only reinforces the workflow without clarifying parameter relationships or formats.

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 'Upload a part in a multipart upload' with a specific verb and resource. It distinguishes itself from sibling tools like ncloud_put_object (single object upload) and ncloud_complete_multipart_upload (finalization) by explicitly mentioning the multipart context.

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 explicitly lays out the sequence: initiate multipart upload first, then upload parts, then complete. This gives clear usage context. However, it does not mention when to avoid this tool or compare against alternatives such as ncloud_put_object for small objects.

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