oci_os_delete_bucket

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions only that the bucket must be empty, but does not disclose that deletion is permanent, what permissions are needed, or what happens if the bucket is non-empty. This is a significant gap for a destructive 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?

The description is a single six-word sentence that is front-loaded and free of any unnecessary words. Every word contributes to clarity, making it highly concise and well-structured.

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 tool with no annotations and no output schema, the description covers the core purpose and the critical empty-bucket precondition. However, it omits important context such as the permanence of deletion and error behavior on non-empty buckets, leaving some gaps but still adequate for a simple tool.

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 fully describes both parameters: bucket_name (required) and compartment_id (optional, defaulting to tenancy). The tool description adds no additional meaning to these parameters, so the schema provides the semantics, meeting the baseline for 100% schema coverage.

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 tool deletes an empty Object Storage bucket, using a specific verb and resource, and the 'empty' qualifier adds important scope that distinguishes it from simply deleting any bucket. This makes the purpose unambiguous compared to sibling tools like create or list.

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 implies the tool is used for deleting empty buckets but does not explicitly specify when to use it over alternatives, nor does it mention prerequisites beyond the bucket being empty. The use case is evident from the verb, but guidance is minimal and not explicitly stated.

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