Reset user password

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

Annotations already mark destructiveHint=true and readOnlyHint=false. The description adds 'Requires confirmation' but does not explain what that entails (e.g., does confirm parameter act as a safeguard?), nor does it mention side effects like session invalidation or authentication requirements.

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?

Extremely concise (two sentences, 10 words) with no unnecessary content. However, priority information is front-loaded. Slightly more detail could be added without hurting conciseness.

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?

No output schema and 0% param coverage; the description fails to explain return values, success/failure behavior, or the role of the 'confirm' parameter. For a mutation tool with side effects, this is insufficiently 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?

Schema coverage is 0% and the description does not explain any parameter purpose beyond their names. 'temporary' and 'confirm' lack context; the description hints at confirmation but doesn't link to the parameter. No added value beyond the schema.

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 ('Set a new password') and identifies the resource ('a user'), with the added context 'Requires confirmation.' This distinguishes it from sibling tools like user_update or user_create.

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 guidance on when to use this tool versus alternatives (e.g., keycloak_user_update), no prerequisites, and no exclusions. The description does not help the agent decide between resetting a password and other user modifications.

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