supabase_list_tables

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

With no annotations provided, the description carries the full burden. It discloses pagination support and return structure (table names, schemas, metadata) but fails to mention safety characteristics (read-only), permission requirements, or what constitutes 'basic metadata'.

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?

Two efficient sentences with no wasted words. The purpose and return values are front-loaded immediately after the [UNIFIED] tag. Every sentence earns its place.

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?

Adequate for a basic listing tool but incomplete given the lack of annotations and 0% schema coverage. The description compensates for missing output schema by describing returns, but leaves parameters largely unexplained and omits behavioral safety details.

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%, requiring the description to compensate. While 'pagination' implies limit/offset usage, the description completely omits explanation of the required 'site' parameter and the 'schema' filter parameter, leaving critical inputs undocumented.

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 tables in the database' and mentions pagination and return values (table names, schemas, basic metadata). However, it does not explicitly differentiate from similar sibling tools like supabase_get_table_schema or supabase_list_schemas.

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 (e.g., when to use pagination vs. querying specific tables) or any prerequisites. The '[UNIFIED]' prefix offers no actionable guidance.

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