supabase_create_table

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

No annotations provided, so description carries full disclosure burden. 'Create' implies mutation but does not specify failure behavior on duplicate names, the security implications of enable_rls defaulting to true, or return value structure. Missing critical behavioral context for a database schema mutation tool.

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 short sentence is efficient but underspecified for complexity. The '[UNIFIED]' prefix appears to be implementation metadata leaking into the description without adding user value. Structure is simple but insufficiently informative.

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?

Inadequate for a 5-parameter mutation tool with zero schema documentation and no output schema. The nested columns array (containing objects with unspecified structure) and security-critical enable_rls parameter warrant detailed explanation entirely absent here.

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 coverage is 0%, requiring heavy description compensation. While 'with specified columns' hints at the columns parameter, the description fails to explain: what 'site' refers to (project identifier?), that 'schema' defaults to 'public', or the meaning of 'enable_rls' (Row Level Security). Four of five parameters remain semantically opaque.

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?

States 'Create a new database table with specified columns' providing clear verb+resource. However, the '[UNIFIED]' prefix is metadata noise without explanation, and the description does not explicitly differentiate from sibling tools like supabase_drop_table or supabase_list_tables despite clear naming distinctions.

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 versus alternatives (e.g., supabase_execute_sql for raw table creation), no mention of prerequisites (e.g., schema existence), and no warnings about existing table conflicts.

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