supabase_test_function

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

With no annotations provided, the description carries the full burden of disclosure but fails to clarify critical behavioral traits. It does not state whether testing executes the function logic against live resources (side effects), requires special permissions, or follows different rate limits than standard invocation.

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 sentence that is otherwise efficient, but the '[UNIFIED]' prefix appears to be internal metadata that consumes valuable space without adding actionable context for the agent, slightly diminishing the signal-to-noise ratio.

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 an output schema, the description is insufficient for a 4-parameter tool. It mentions returning 'the response' but fails to explain the critical required parameters or distinguish usage patterns from similar tools in the extensive sibling list.

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 description coverage is 0%, requiring the description to compensate significantly. While it hints at the 'test_data' parameter via 'sample data', it completely omits semantics for required parameters 'site' (likely a project reference) and 'function_name', and offers no context for the 'method' parameter's valid values.

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 action ('Test') and resource ('Edge Function'), and distinguishes this from sibling invocation tools (supabase_invoke_function) by using the specific verb 'Test' rather than 'Invoke'. However, the '[UNIFIED]' prefix adds noise without explanation, and it does not clarify the semantic difference between testing versus production invocation.

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 instead of the sibling supabase_invoke_function variants or supabase_check_function_health. It does not indicate if this is for development debugging, CI/CD pipelines, or pre-deployment validation.

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