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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the mutation/safety profile is covered. The description adds a genuine behavioral fact beyond the annotations: execution requires user approval of the exact request in BEON PASS. It does not disclose what gets overwritten or the reversibility of config changes, keeping it short of a 5.

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?

Two lean sentences, front-loading the operation and following immediately with the execution prerequisite. No filler or redundancy.

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 destructive, open-world mutation tool with 9 parameters at 0% schema coverage and no output schema, this description is far too thin. It covers the approval gate but leaves parameter semantics, scope of change, and reversibility entirely undocumented.

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% across 9 parameters including a nested config object, so the description must carry the burden but doesn't. It loosely gestures at the field categories (signup, redirect, email, password, token lifetime) but explains no parameter meaning, and completely omits the required project_ref and the cryptic approval_id / beon_* workflow parameters.

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 states a specific verb+resource ('Update ... configuration') and enumerates the affected areas (signup, redirect, email, password, token lifetime), which maps well to the actual config fields. It does not explicitly name the read counterpart supabase_get_auth_config, so it stops short of full sibling differentiation.

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?

It states the BEON PASS approval prerequisite, which is a real usage condition. However it gives no when-to-use vs when-not guidance and never contrasts with supabase_get_auth_config or other config-update siblings, relying on the tool name alone to imply usage.

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