supabase_get_function_url

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Get' implies a read-only operation, it does not clarify whether this requires network authentication, what format the URL is returned in, or whether the URL includes required auth tokens/anonymous keys.

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 brief at one sentence. The '[UNIFIED]' prefix is unnecessary metadata cruft, but the core message is efficiently structured without redundant content.

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 0% schema coverage, lack of annotations, and absence of output schema, the description should explain parameter meanings and return format. It provides only the minimal operation definition, leaving significant contextual gaps for an agent attempting to invoke the tool correctly.

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% (no descriptions for 'site' or 'function_name'), and the description provides no compensation. It fails to explain that 'site' likely refers to the project identifier or that 'function_name' is the deployed edge function's name, leaving both parameters semantically 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 verb (Get) and resource (full URL for invoking an Edge Function). However, it does not explicitly distinguish from sibling tools like `supabase_invoke_function` (which actually executes the function) versus this tool which only retrieves the endpoint 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?

The description provides no guidance on when to use this tool versus the various invoke alternatives (supabase_invoke_function, supabase_invoke_function_get) or when obtaining the raw URL is preferable to invoking directly. No prerequisites or conditions are mentioned.

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