supabase_get_storage_stats

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

No annotations provided, so description carries full disclosure burden. While it lists returned data categories, it fails to state whether this is a read-only operation, requires specific permissions, or has rate limiting implications. The agent cannot determine operational safety from the description alone.

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?

Single sentence format is appropriately concise and front-loaded with the action. The '[UNIFIED]' prefix appears to be metadata leakage but doesn't significantly impair readability. However, extreme brevity comes at the cost of omitting necessary parameter documentation.

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?

Without output schema or annotations, the description remains inadequate. The undocumented 'site' parameter is critical for invocation, and behavioral context (permissions, scope) is missing. For a statistics retrieval tool with no structured output schema, the description should compensate with richer behavioral context.

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 for the required 'site' parameter. The description completely omits what 'site' represents (e.g., project reference, URL, identifier) or valid formats, leaving the agent without guidance for the only input parameter.

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?

Clear specific verb ('Get') + resource ('storage statistics') with precise scope details ('bucket count, total files, and usage information'). Distinguishes from sibling tools like 'supabase_get_bucket_stats' by emphasizing aggregate storage-wide metrics rather than per-bucket statistics.

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 similar siblings such as 'supabase_get_bucket_stats' or 'supabase_list_buckets'. Missing prerequisites or conditions that would help an agent select this over alternatives.

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