supabase_storage_create_bucket

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

Annotations already provide readOnlyHint=false and destructiveHint=true, but the description adds no additional behavioral context (e.g., whether it overwrites, requires unique names, or returns a bucket object). The description neither contradicts nor enriches the annotations, leaving the agent with only the minimal high-level statement.

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, grammatically complete sentence with no redundancy. It is appropriately brief for a simple operation, though it omits additional context; this is conciseness, not under-specification.

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?

With no output schema and only a five-word description, the tool lacks critical context about return values, error behavior, or idempotency. The annotations hint at destructiveness but do not clarify the creation result, making the description incomplete for an agent to predict outcomes beyond the basic action.

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 has 100% coverage with clear descriptions for all four parameters, so the schema carries the semantic load. The description adds no extra parameter-level detail, so the baseline of 3 is appropriate for high coverage.

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 'Create a new storage bucket' uses a specific verb and resource, clearly stating the action and object. It distinguishes from sibling storage actions like list, upload, download, and delete by naming the create operation for buckets.

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?

No guidance on when to use this tool versus alternatives such as supabase_storage_list_buckets or supabase_storage_upload. There is no mention of prerequisites, use cases, or exclusions, leaving the agent without contextual direction.

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