supabase_delete_user_factor

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. While 'Delete' implies a destructive mutation, the description fails to state whether this action is reversible, whether it immediately logs the user out, or what the return value structure looks like.

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 efficient sentence with no wasted words. However, the '[UNIFIED]' prefix appears to be metadata noise that does not aid agent understanding, slightly detracting from an otherwise perfectly concise statement.

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 operation with three undocumented required parameters, no output schema, and no annotations, the description is inadequate. It identifies the action but provides no guidance on parameters, side effects, or success/failure indicators necessary for safe invocation.

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 for all three required parameters (site, user_id, factor_id), the description completely fails to compensate. It does not explain what these parameters represent, their formats, or how to obtain valid values (e.g., that factor_id references a specific MFA enrollment).

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 '[UNIFIED] Delete an MFA factor from a user' provides a specific verb (Delete), resource (MFA factor), and scope (from a user). It clearly distinguishes from siblings like `supabase_delete_user` (which deletes the entire user) and `supabase_list_user_factors` (which reads rather than deletes).

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?

No explicit when-to-use guidance is provided. The description fails to mention prerequisites (e.g., that factor_id must be obtained first via `supabase_list_user_factors`) or compare this tool to alternatives like disabling factors versus deleting them.

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