ncloud_put_object

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

With no annotations, the description carries the burden of disclosure. It only states the basic operation and dryRun feature, omitting important behaviors like overwrite semantics, error conditions, size limits, or required bucket existence.

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 extremely concise with two sentences, no unnecessary words, and all sentences add direct value.

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 upload tool, the description covers the primary action, but lacks details on preconditions (bucket existence), return values (no output schema), and error handling. Parameter hints for contentType are missing.

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%, so the baseline is 3. The description adds little beyond offering dryRun hint, which is already defined in the schema. No additional context is provided for other parameters like contentType or key.

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 ('Upload (put) an object') and the resource ('Object Storage bucket'), effectively distinguishing it from sibling tools like ncloud_get_object or ncloud_delete_object.

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 implies usage for uploading objects and mentions dryRun for preview, but does not provide explicit guidance on when to use this tool versus alternatives like ncloud_ncs_put_object or multipart upload tools.

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