supabase_list_edge_functions

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 that the tool 'reads from the functions volume,' implying a read-only operation and revealing the data source, but lacks explicit safety guarantees, rate limits, or error behavior.

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 appropriately concise with two sentences and the main action front-loaded. The '[UNIFIED]' prefix appears to be internal metadata noise but does not significantly detract from readability.

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?

For a single-parameter list tool without output schema, the description provides adequate operational context (self-hosted scope, data source), but the complete omission of the required 'site' parameter documentation creates a critical gap for correct invocation.

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 fails to compensate by explaining what 'site' represents (e.g., project ID, URL) or providing an example, leaving the parameter completely 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[s] all deployed Edge Functions' and specifies the scope is 'Self-Hosted' environments. However, it does not explicitly differentiate from the sibling tool 'supabase_list_functions', leaving ambiguity about which to use.

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 note about Self-Hosted implies a specific usage context, but there is no explicit guidance on when to use this versus 'supabase_list_functions' or what prerequisites (e.g., self-hosted configuration) are required.

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