supabase_invoke_function_batch

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention critical batch operation behaviors: execution order (parallel vs sequential), partial failure handling (all-or-nothing vs individual failures), return value structure, or timeout implications across multiple invocations.

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 two sentences with the core purpose front-loaded. However, the '[UNIFIED]' tag at the beginning is structural noise that doesn't help the agent understand or select the tool.

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 batch processing tool with no output schema and zero parameter descriptions, the description is insufficient. It lacks essential context about error handling patterns, response aggregation, and execution guarantees that agents need to safely invoke batch operations.

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 fully compensate but only partially does. It implies the 'payloads' array through 'different payloads', but provides no semantic information about 'site' (format/scope) or 'function_name' (identifier format), nor does it describe the expected structure of items within the payloads array.

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 core action ('Invoke an Edge Function') and the distinguishing scope ('multiple times with different payloads'), distinguishing it from single-invocation siblings like 'supabase_invoke_function'. However, it doesn't explicitly name the alternative tool, and the '[UNIFIED]' prefix adds noise without semantic value.

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 phrase 'Useful for batch processing' provides implied context, but there is no explicit guidance on when to use this versus 'supabase_invoke_function' for single calls, or warnings about when batching might be inappropriate (e.g., large payload sizes, rate limits).

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