supabase_storage_delete

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

The annotations include destructiveHint=true, so the destructive nature is already disclosed. The description merely says 'Delete' without adding extra behavioral context like permanence, partial failure, or permission requirements. It is consistent with annotations but contributes no additional transparency.

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, front-loaded sentence with no unnecessary words. Every word earns its place.

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, the combination of description, schema (100% coverage), and destructiveHint annotation covers the essential context. It lacks explicit mention of irreversibility or behavior for missing files, but these are not critical given the annotation disclosure.

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 describes both parameters (bucket and paths) with clear descriptions, giving 100% coverage. The description adds no parameter-specific details, so baseline 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 'Delete files from a storage bucket' clearly identifies the verb (delete), resource (files), and location (storage bucket). It distinguishes this from sibling supabase_delete (database rows) and other storage operations like move/upload.

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 provides no guidance on when to use this tool versus alternatives such as supabase_delete or supabase_storage_move. No exclusions, prerequisites, or alternative scenarios are mentioned.

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