supabase_get_function_info

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

No annotations are provided, so the description carries the full burden. While 'Get' implies a read-only operation, the description does not explicitly state safety guarantees, idempotency, potential errors, or what specific data structure is returned. It mentions 'configuration' but not what that encompasses.

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 a single efficient sentence with no filler. The [UNIFIED] prefix appears to be a metadata tag. Every word earns its place; there is no waste.

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?

Given the lack of annotations, output schema, and parameter descriptions, the description is insufficiently complete. For a retrieval tool with no structured return documentation, it should at least hint at the return value structure or key fields returned (e.g., configuration details, status, etc.).

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?

With 0% schema description coverage, the description must compensate but only partially does. 'Specific Edge Function' implies the function_name parameter, but the 'site' parameter (likely identifying the Supabase project/instance) is completely undocumented. No parameter formats, constraints, or examples are provided.

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 uses a clear verb ('Get') and resource ('information about a specific Edge Function'), and adds scope with 'including its configuration'. However, it does not explicitly differentiate from siblings like supabase_list_edge_functions or supabase_get_function_url, though 'configuration' implies more detail than just a URL.

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 is provided on when to use this tool versus alternatives such as supabase_list_edge_functions (for listing all functions) or supabase_get_function_url (for just the endpoint URL). The description states what it does but not the selection criteria.

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