supabase_empty_bucket

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

No annotations provided, so description carries full burden. While 'Delete' implies destructive behavior, the description omits critical details: whether deletion is permanent/irreversible, if it affects nested folders recursively, immediate storage quota impact, or confirmation requirements. Insufficient for a bulk 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?

Extremely concise with only two sentences. Front-loaded with the core action. Deduction for the '[UNIFIED]' prefix which appears to be metadata leakage rather than descriptive content, though it doesn't significantly obscure the meaning.

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?

Minimum viable for a simple bucket operation. Acknowledges the prerequisite relationship with delete_bucket. However, given zero schema documentation and lack of output schema, the description should have elaborated on parameter meanings and deletion scope (recursive vs shallow).

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 has 0% description coverage (both 'site' and 'bucket_id' undocumented). Description fails to compensate by explaining parameter semantics—particularly 'site' which is ambiguous (could mean project ID, URL, or reference)—nor does it clarify bucket_id format requirements.

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?

States specific verb ('Delete') and resource ('all files in a bucket'). The phrase 'Use before delete_bucket' clearly distinguishes this from the sibling supabase_delete_bucket tool, clarifying that this empties contents while the sibling removes the container.

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?

Provides explicit sequencing guidance ('Use before delete_bucket') establishing the workflow prerequisite. However, lacks explicit 'when not to use' guidance (e.g., when selective file deletion via supabase_delete_files is preferred over bulk deletion).

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