initiate_password_reset

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

The description adds important context beyond annotations: 'Always returns success to prevent user enumeration' and 'via Supabase Auth', which are not captured by readOnlyHint, idempotentHint, or destructiveHint.

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 concise sentences that each add value: the first defines the action, the second explains the behavior. No wasted words.

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 single-parameter tool with no output schema and annotations covering idempotency/non-destructiveness, the description adequately covers the key behavioral trait and mechanism, though it omits rate limits or prerequisites.

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?

The sole parameter 'email' has no description in the schema (0% coverage) and the description provides no additional details about format, validation, or constraints.

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 ('Send a password reset link') and the resource ('user's email via Supabase Auth'), distinguishing it from siblings like 'complete_password_reset'.

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 the key behavior that it always returns success, implying no error-based feedback, but does not explicitly state when to use this tool versus alternatives like 'initiate_account_recovery' or 'complete_password_reset'.

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