edge_invoke_function

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

With no annotations, the description bears full responsibility for disclosing side effects, authentication needs, or invocation behavior. It only states the action, omitting that invoking a function may execute code with side effects or return data. This is a meaningful transparency gap for a potentially mutating operation.

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 filler. It communicates the core action efficiently, earning a high score for conciseness and structure.

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 is simple (3 params, no output schema), but the description fails to explain expected return values, response format, errors, or side-effect implications of invoking a function. With no output schema and minimal context, the description is not sufficiently complete for an agent to anticipate invocation outcomes.

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 provides full descriptions for all three parameters (function_name, headers, payload), so coverage is 100%. The description adds no parameter-level detail beyond the schema, which matches the baseline for high schema coverage.

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 specific verb ('Invoke') and resource ('Supabase Edge Function'), clearly indicating the tool's action. It distinguishes from sibling tools (list, deploy, remove) through the verb, though it does not elaborate on what invoking entails.

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 gives no guidance on when to invoke a function versus listing, deploying, or removing one. There is no mention of prerequisites, function readiness, or scenarios where this tool is appropriate.

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