get_s3_incomplete_multipart_uploads

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

No annotations are provided, so the description carries full burden. It discloses that the tool identifies buckets and wasted storage, but does not state if it modifies state, required permissions, or rate limits. For a read-only audit tool, the description lacks explicit safety signals.

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?

Efficiently structured: core purpose in first sentence, cost implications, fix, and parameter description. Examples are relevant and front-loaded. Every sentence adds value, with no redundancy or fluff.

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 explains output conceptually (list of buckets and wasted storage) but lacks details on return structure, e.g., whether it returns bucket names, storage amounts, or pagination. Given no output schema, additional clarity on results format would improve completeness.

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 single optional parameter 'older_than_days' is explained with its purpose ('Flag uploads older than this many days') and default value. Schema coverage is 0%, so the description adds value beyond the schema definition. Could be more explicit about how the flagging works (e.g., filtering vs threshold setting).

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?

Clearly states the tool finds S3 buckets with incomplete multipart uploads older than a threshold. The verb 'find' and resource 'S3 buckets with incomplete multipart uploads' are specific and distinct from sibling audit tools like 'audit_s3_intelligent_tiering' or 'scan_s3_bucket_key_opportunities'.

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?

Provides context on when to use (incomplete uploads accumulating storage costs) and outlines the fix (S3 lifecycle rule). Does not explicitly state when NOT to use or offer alternative tools, but the cost-saving context is clear and the sibling list includes related audits.

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