supabase_get_database_size

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation via 'Get', but fails to specify return format (bytes vs MB), whether the operation is expensive/slow on large databases, or what specific size metrics are returned (total only, per-table breakdown, index sizes?).

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 brief (one sentence), but the '[UNIFIED]' prefix adds noise without value. The core message is front-loaded, though the brevity comes at the cost of 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?

Despite having only one parameter, the tool is inadequately documented due to 0% schema coverage and no output schema. The description omits critical context about the 'site' parameter and return value structure that an agent needs to invoke the tool correctly.

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 description coverage is 0% for the required 'site' parameter, and the description provides no compensation. It does not explain what 'site' refers to (project reference ID, URL, name?), expected format, or where to obtain this value.

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 states the basic purpose (retrieving database and table sizes) with a clear verb and resource, but fails to differentiate from the sibling tool 'supabase_get_database_stats', leaving ambiguity about which tool to use for size-related queries.

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 provided on when to use this tool versus alternatives like 'supabase_get_database_stats' or 'supabase_get_storage_stats'. No prerequisites or conditions are mentioned.

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