supabase_list_buckets

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

No annotations are provided, so the description carries the full burden. It discloses return values (bucket names, public/private status, settings) which is helpful given the lack of output schema, but fails to mention safety traits, required permissions, or side effects.

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 appropriately brief with two clear sentences. The '[UNIFIED]' prefix is unnecessary noise, but the core content is front-loaded and efficient.

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 tool with a single parameter and simple read-only behavior, the description is incomplete. It lacks critical parameter documentation and provides no behavioral context beyond the return structure, leaving significant gaps given the absence of annotations.

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 for the required 'site' parameter, the description must compensate but completely omits any explanation of what 'site' represents (e.g., project ID, URL, or site name) or how to format it.

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 'List all storage buckets' with a specific verb and resource. It implicitly distinguishes from sibling tools like 'supabase_get_bucket' (singular) and 'supabase_list_files' (different resource), though it does not explicitly name alternatives.

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_get_bucket' for retrieving a single bucket, or prerequisites like required permissions.

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