reset_password

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

With no annotations provided, the description carries the behavioral transparency burden. It discloses the key behavior of generating and returning a password when omitted, and emphasizes the out-of-band delivery requirement. However, it does not mention potential side effects like invalidating existing sessions or what happens on failure.

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 two sentences, front-loaded with the primary action, and contains no fluff. Every sentence adds critical information: the core purpose and the optional-password behavior with a security instruction.

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?

The description covers the main usage scenario and the special case of omitted new_password, but it lacks important context for a mutation tool, such as whether the reset takes immediate effect, side effects like logging out existing sessions, or behavior on invalid user IDs. This is partially mitigated by the schema's details on new_password.

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 schema covers one of two parameters (new_password) with a detailed description, but user_id lacks any description. The tool description does not add meaning for user_id beyond the tool name's implication, and it merely repeats the new_password behavior already described in the schema. With only 50% schema coverage, the description should compensate but does not.

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 tool resets a user's password, with a specific verb and resource. It also distinguishes behavior based on the optional new_password parameter, making the purpose unambiguous.

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 gives clear context on when to use the tool (to reset a password) and includes an important guideline: if no new_password is provided, the generated password must be forwarded to the user out-of-band. It does not explicitly mention alternatives, but no sibling tool offers similar functionality.

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