s3_delete_bucket

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

Annotations already carry destructiveHint=true, so the description adds value by specifying exactly what gets destroyed: 'все файлы бакета будут удалены' (all bucket files will be deleted). This concrete consequence goes beyond the generic annotation and is essential for an agent assessing risk.

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 short and front-loads the destructive warning, which is appropriate for a high-risk operation. The parenthetical '(s3/delete_bucket)' is slightly redundant with the tool name, but it does not undermine clarity.

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 delete operation with a required confirm flag, the combination of description, schema, and annotations is sufficiently complete: the scope of destruction is explicit, the required parameter is documented in the schema, and the lack of an output schema is acceptable for a simple delete call.

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 the baseline is 3. The description adds no parameter-level detail beyond the schema, but none is required because each parameter (bucket, confirm, account_id) is already documented in the input schema.

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 and resource: 'Удалить бакет из S3-аккаунта' (delete bucket from S3 account), which clearly states what the tool does. It also includes the API method path (s3/delete_bucket) and is easily distinguishable from siblings like s3_delete_file or delete_iso_image because it names the bucket as the target.

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 intended use is implied by the resource type and name—use this to delete a bucket—but there is no explicit guidance about when NOT to use it or which alternative to choose. It does not mention sibling tools like s3_delete_file or s3_delete_account, so the routing is left to inference.

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