supabase_storage_download

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

The description reveals that the tool returns base64-encoded content, a key behavioral detail that goes beyond the annotations. The readOnlyHint and idempotentHint annotations align with this read operation, with no contradictions. It does not cover error conditions or permission requirements, but for a read-only operation this is acceptable.

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, concise sentence that immediately states the action and key output detail. Every word earns its place, with no repetition of schema or annotation information.

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 only two required parameters and a simple read operation, the description covers the essential behavior and return format. The output schema is absent, but the description explicitly notes 'returns base64', filling that gap. Annotations provide safety and idempotency context, making this adequately complete for the tool's complexity.

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?

Both parameters (bucket and path) are fully described in the schema with clear explanations ('Bucket name', 'File path within the bucket'). The tool description adds no additional parameter information, so the schema already provides complete semantic coverage, meriting a baseline score of 3.

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 uses the specific verb 'Download' with a clear resource 'file from a storage bucket'. The parenthetical '(returns base64)' distinguishes this from sibling tools like supabase_storage_get_public_url or supabase_storage_delete, making the purpose unambiguous.

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 implies the tool is used when you need the actual file content, but it does not explicitly state when to use this versus alternatives like get_public_url or list_files. There is no mention of exclusions or preferred use cases, so guidance is limited to implied usage.

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