timeweb_delete_s3_storage

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

With no annotations provided, the description carries the full burden. It discloses the irreversible nature via 'permanently', but omits other behavioral details such as whether confirmation is needed, what happens to contained objects, or permission requirements. 'Permanently' offers some value but is minimal.

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 a single, tightly worded sentence with no filler or repeated schema information. 'Permanently' earns its place by adding meaningful context. It is optimally concise.

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 with one required parameter and no output schema, the description covers the core action and key warning (permanence). However, it does not mention expected response behavior, edge cases, or any impact on related resources, leaving some gaps for an agent.

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 already covers both parameters (bucket_id with type and description, format with enum and description), giving 100% coverage. The description adds no parameter-specific semantics, so the baseline score of 3 is appropriate.

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 ('Delete') and clearly identifies the resource ('S3 storage bucket'), and the adverb 'permanently' adds clear scope. It distinguishes itself from sibling tools like timeweb_delete_server or timeweb_delete_database by explicitly naming S3 storage.

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 use case is implicitly clear: use when you want to delete an S3 bucket. No explicit exclusions, alternatives, or prerequisites are mentioned, but the context is straightforward for a delete operation.

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