s3_list_multipart_uploads

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

Annotations already cover the safety profile with readOnlyHint, idempotentHint, and destructiveHint=false. The description adds useful context by specifying 'in-progress' and 'S3-compatible', but it does not disclose that results are paginated through maxUploads/keyMarker/uploadIdMarker, despite saying 'List all'.

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?

A single sentence with no filler, front-loading the verb and resource. It is as short as possible while still conveying the tool's scope and S3 compatibility.

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?

There is no output schema, but the description never explains the response shape or how pagination works, so an agent cannot fully anticipate what the tool returns. The presence of two 'Pagination cursor' parameters implies paging, but the description gives no guidance on how to traverse pages to actually list 'all' uploads.

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 description adds no parameter-level meaning beyond the schema; 'for a bucket' merely recontextualizes the required bucket parameter. With 67% schema coverage, the missing delimiter and maxUploads semantics are not compensated for by the description.

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 uses a specific verb ('List') with a clear resource ('in-progress S3-compatible multipart uploads') and a clear scope ('for a bucket'). It distinguishes itself from sibling s3_list_parts, which lists parts of a specific upload, and from b2_unfinished_uploads by emphasizing S3 compatibility.

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 action itself implies when to use it (when in-progress multipart uploads need enumeration), but it gives no explicit alternatives or exclusions. It does not tell the agent to prefer s3_list_parts for a single upload or to use abort/complete operations for finalization, so routing relies on inference.

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