s3_abort_multipart_upload

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

Annotations already indicate destructiveHint=true, so the description is not required to restate destructiveness. It adds useful behavioral context by specifying that the operation aborts an in-progress upload and releases associated storage, making the consequence concrete beyond the bare 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, tightly constructed sentence that communicates the action, scope, and consequence with no redundant words. It is front-loaded and easy to parse.

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 destructive operation, the description plus annotations and 100% schema parameter coverage provide enough information to invoke the tool correctly. It would benefit from a brief note about irreversible consequences or the distinction from s3_complete_multipart_upload, but those are either covered by annotations or inferable from the sibling tool names.

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%, and every parameter, including the important confirm flag, already has a meaningful schema description. The tool description itself adds no parameter-specific detail, so the baseline 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 uses a specific verb ('Abort') with a clear resource ('in-progress S3-compatible multipart upload') and an outcome ('release all associated storage'). This clearly distinguishes it from related operations like s3_complete_multipart_upload or s3_create_multipart_upload.

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 word 'in-progress' implies this tool is for canceling an unfinished multipart upload rather than completing it, which gives some usage context. However, it does not explicitly state when to choose this over s3_complete_multipart_upload or s3_delete_object, nor does it mention any exclusions.

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