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

Annotations already declare destructiveHint=true, but the description goes well beyond them: it discloses that the call refuses without confirm and 'nothing happens', that the access key is deleted, that S3_* variables are unset, and that the app restarts before the bucket is removed. This is exactly the extra behavioral context an agent needs for an irreversible operation.

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?

Front-loaded with the destructive scope, then the confirmation protocol, then side effects, then the alternative. Every sentence carries information, though the confirm-gate wording slightly duplicates the schema's own description of that parameter.

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?

With an output schema present, return values need no explanation, and the description still covers the mutation's blast radius, side effects, restart ordering, and failure mode. Nothing an agent needs to call this safely is missing.

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 coverage is 100% and the confirm parameter is already fully documented in the schema, including the 'ask first, and stop' nuance. The description reinforces the confirm gate but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Delete a project's S3 bucket') and immediately scopes it ('with every file in it, for good'), so an agent knows exactly what is destroyed. It also names the sibling it is not (rotate_storage_key), which differentiates it from the add_storage/remove_storage family without opening a schema.

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 an explicit when-to-use protocol: reply that files are gone, ask for confirmation, stop, then call with confirm: true only after a yes. It also names the alternative route for a leaked key (rotate_storage_key). Both the condition and the exclusion are spelled out.

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