supabase_list_functions

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

No annotations provided, so description carries full burden. Mentions 'pagination' implying paginated results, but lacks critical behavioral details: return format/schema, whether results include function bodies or just metadata, rate limits, or authentication requirements. 'Read-only' nature is implied but not stated.

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 is appropriately brief. However, the '[UNIFIED]' prefix appears to be implementation metadata rather than descriptive content, slightly cluttering the front-loading.

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?

Insufficient for a 4-parameter pagination tool with no output schema or annotations. Critical gaps: unexplained 'site' parameter, no indication of what constitutes a 'database function' in this context (SQL functions vs stored procedures), and no return value documentation.

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%, so description must carry full load. It indirectly explains 'schema' ('in a schema') and 'limit/offset' ('pagination'), but provides no information about the required 'site' parameter (likely a project identifier). Baseline compensation for undocumented schema is partial.

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 verb ('List') and resource ('database functions/stored procedures') with scope ('in a schema'). Effectively distinguishes from sibling 'supabase_list_edge_functions' by specifying 'database functions/stored procedures', though it doesn't clarify when to choose this over other database listing tools like supabase_list_tables.

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 (e.g., supabase_get_function_info for single function details), nor any prerequisites like required permissions or connection setup for the 'site' parameter.

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