Supabase Set Secret

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

Adds meaningful context beyond the annotations: 'server-side only', 'live write, needs human approval', and the approval round-trip that yields an approval_required refusal. The annotations already declare destructive/idempotent/openWorld, and the description does not contradict them, but it could say more about overwrite behavior for an existing secret name.

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?

Three short, front-loaded lines covering what it does, when to use it, and what it returns. Every sentence earns its place with no filler.

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?

Despite an output schema existing, the description still surfaces the two possible outcomes ({ok, name} vs approval_required refusal), and the approval workflow is fully described. Nothing an agent needs to invoke it correctly is missing.

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 100%, so the baseline is 3. The description adds workflow-level meaning by tying the approval_required refusal to the retry-with-approval_id pattern and by stressing that the value is never echoed, which helps the agent interpret the required params and the optional approval_id.

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?

States a precise verb+resource+scope: 'Write one edge-function secret on a Supabase project'. It explicitly distinguishes itself from the bulk alternative ('backend_deploy sets the standard set for you'), so an agent can choose between them without opening a schema.

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?

Provides an explicit 'Use when' clause with a concrete example (adding a single secret such as FAL_KEY) and names the alternative tool for the batch case. When-to-use and when-not-to-use are both covered.

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