edge_deploy_function

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

With no annotations, the description must carry the full behavioral burden. It only states 'Deploy an Edge Function to Supabase,' which implies a write operation but provides no details on idempotency, side effects, permissions required, or the shape of the response. This is a significant transparency gap for a deployment action.

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, front-loaded sentence with no redundant information. However, it is under-specified for the tool's complexity, so while it is concise, it sacrifices necessary detail. Given the brevity, a score of 4 is appropriate.

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?

The tool has no output schema and no annotations, so the description should explain what happens on deployment, the return value, and error conditions. None of this is provided. The description is adequate for identifying the tool but not for understanding its full behavior or side effects.

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?

The input schema already provides 100% coverage of the three parameters with clear descriptions ('function_name', 'function_code', 'import_map'). The tool description adds no additional semantic value beyond what the schema already specifies, so the baseline score of 3 applies.

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 the specific verb 'Deploy' with a clear resource ('Edge Function') and target ('Supabase'). This differentiates it implicitly from sibling tools like edge_invoke_function, edge_list_functions, and edge_remove_function, though it does not explicitly name them.

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 the sibling edge function tools. It does not mention prerequisites such as authentication, whether this creates or updates an existing function, or any scenarios where the other tools should be preferred.

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