s3_delete_object

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

With no annotations, the description carries full responsibility for behavioral disclosure. It clearly warns that the action is 'Irreversible', marks it as reserved for dangerous guard mode, and requires confirmation. This covers the most critical behavioral traits, though it omits details like permission requirements or error behavior.

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?

Two sentences: the first states purpose, the second delivers the safety warnings. Every word earns its place, front-loading the action and then the critical guardrails with no redundancy.

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 operation with comprehensive schema coverage and no output schema, the description is complete: it covers purpose, irreversibility, restricted use, and required confirmation. No additional context is necessary.

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 input schema covers all four parameters with descriptions, so the schema already provides full parameter semantics. The description adds little beyond reinforcing the confirmation requirement, which is a usage guideline rather than new parameter information.

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 verb ('Delete') and resource ('a single object from S3'), specifying the scope as a single object. This distinguishes it from sibling tools like s3_delete_bucket and s3_copy_object, making the purpose unambiguous.

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 provides explicit context for when to use the tool: 'Reserved for dangerous guard mode' and mandates confirmation with the user. While it does not explicitly name alternatives or state when not to use, the guard-mode restriction and confirmation requirement give strong usage guidance.

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