s3_delete_object

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

No annotations are provided, so the description carries full burden. It explicitly states the operation is 'Irreversible' and emphasizes the need for confirmation, giving clear behavioral context beyond the basic schema.

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 concise with three sentences, each serving a distinct purpose: stating the core action, noting irreversibility, and providing usage guidance. No redundant or extraneous information.

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 delete tool, the description covers the essential context: what it does (delete), consequences (irreversible), usage restrictions (dangerous mode), and required confirmation. No output schema is needed for such a straightforward operation.

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%, so baseline is 3. The description adds value by linking the three parameters (provider, bucket, key) to the confirmation requirement, reinforcing their critical role in the irreversible delete action.

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 'Delete a single object from S3,' using a specific verb and resource. It distinguishes from sibling tools like s3_copy_object or s3_move_object, and the scope (single object) is explicitly mentioned.

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 specifies that the tool is 'Reserved for dangerous guard mode' and mandates 'ALWAYS confirm with the user (provider, bucket, key) before calling.' This provides explicit when-to-use context and a critical usage requirement, effectively differentiating it from safer alternatives.

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