Create Users Forgot Password

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

No annotations exist, so the description carries the full disclosure burden. It states the primary side effect (sending an email with a reset link) but omits related behaviors such as token generation/expiry, behavior for unknown emails, or whether existing reset links are invalidated.

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?

One short sentence with no filler; the action and recipient are front-loaded. It earns its place.

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 side-effectful action with no annotations and no output schema, the description is sparse. It does not disambiguate from similarly named auth tools or describe the state change/response, leaving an agent without enough context to confidently invoke it.

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%, so the description must explain the parameters. It only hints that the email parameter is the recipient via 'to the user' and says nothing about accept-language or any expected value 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 uses a specific verb ('sends') and resource ('email with a reset link') and identifies the recipient as the user. It is clear but does not explicitly distinguish it from nearby sibling tools like create_users_reset_password or create_admin_users_password_reset_token.

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 when-to-use guidance is provided. There is no mention of when to choose this over create_users_reset_password or create_admin_users_password_reset_token, nor any caveats such as verifying the user exists first.

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