cos_delete_bucket

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

With no annotations, the description carries full burden. It correctly states the destructive nature and the emptiness requirement. Could disclose irreversibility or permission needs, but the core constraint is noted.

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?

A single, front-loaded sentence that immediately communicates action and precondition. No wasted words, making it efficient for quick comprehension.

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?

Covers the essential behavior (delete with emptiness requirement) and parameters. Missing details on return values, error handling, and irreversibility, but for a simple delete tool, it's nearly complete.

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?

No parameter descriptions are provided in the description or schema (0% coverage). The parameter names 'bucket_name' and 'region' offer some hints, but details like required format, default region, or that region may be optional are missing.

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?

Description clearly states the action ('Delete') and resource ('COS bucket'), with a crucial precondition ('must be empty'). This distinguishes it from sibling tools like cos_create_bucket and cos_set_bucket_cors.

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 precondition 'must be empty' provides clear guidance on when the tool can be used. It implicitly advises checking bucket contents before invoking. However, no explicit alternatives are mentioned, though the agent can infer from sibling tools.

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