appwrite_delete_bucket

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

No annotations provided, so description carries full burden. It discloses the critical cascade behavior (files deleted with bucket) but omits other key traits: irreversibility, error handling if bucket doesn't exist, and whether the operation is synchronous or asynchronous.

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?

Two sentences with clear structure: action first, critical warning second. Efficient length. Deduction for the '[UNIFIED]' metadata prefix which serves no semantic purpose for the agent.

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 operation with no output schema and no annotations, the description covers the essential cascade warning but leaves significant gaps: parameter semantics undocumented, irreversibility not stated, and no indication of return value or error states.

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?

With 0% schema description coverage, the description fails to compensate. While 'storage bucket' implies the purpose of bucket_id, the 'site' parameter is completely unexplained. No syntax hints or format examples provided for either parameter.

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?

Clearly states the action (Delete) and resource (storage bucket). The cascade warning ('All files in the bucket will be deleted') effectively distinguishes this from file-level deletion siblings like appwrite_delete_file. The '[UNIFIED]' prefix is noise but doesn't obscure the purpose.

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?

Implies usage context through the cascade warning (use when you want to delete everything), but lacks explicit comparison to alternatives like appwrite_delete_file or appwrite_bulk_delete_files. No guidance on prerequisites or irreversibility.

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