Reset User Password

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

The description discloses key behavioral traits beyond the annotations, such as sending a password-reset email and the ability to disable email via sendEmail=false. Annotations already indicate a non-readonly operation, so the description adds useful side-effect information without contradicting them.

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 relatively concise and front-loaded with the main purpose. Some redundancy exists (e.g., email sending is mentioned twice), but overall it is efficient and easy to scan.

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 tool is simple and the description covers purpose, usage, and parameters adequately. However, the userId discrepancy with the schema and the lack of information about the actual outcome (e.g., whether the password is reset to a temporary value) leave some gaps, making it only minimally complete.

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?

Although the schema has 100% description coverage, the description introduces 'userId' which is not in the schema and states 'at least one required' while the schema marks 'username' as the sole required field. This misinformation undermines the clarity that the schema already provides, making the parameter semantics confusing rather than helpful.

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 that the tool resets a Salesforce user's password and sends a password-reset email, which distinguishes it from sibling tools like sf_freeze_user or sf_update_user. However, it mentions 'username or user ID' while the schema only includes 'username', introducing ambiguity about the actual input scope.

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 an explicit usage context: 'Use when a user is locked out or needs to set a new password.' This helps the agent decide when to invoke the tool. It does not mention alternatives or exclusions, but the context is clear enough for this simple operation.

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