auth_reset_password

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

Goes beyond annotations by disclosing token lifetime (1 hour), single-use semantics, and the side effect of revoking all existing sessions on success — genuinely useful mutation context. Minor tension with idempotentHint=true since a second call with the same single-use token will fail, but the underlying end state is stable, so this is not a true contradiction.

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?

Three short sentences, no redundancy, with the source of the token front-loaded and the consequences (expiry, session revocation) following. Every sentence carries a distinct piece of information.

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?

With no output schema, the description adequately explains the flow and side effects. It omits failure behavior (expired or already-used token) and whether authentication is required to call it, which would be useful for a credential-mutating endpoint.

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 100%, so both 'token' and 'password' (with the 8-character minimum) are already documented. The description adds only the token's provenance, which is largely covered by the schema text; baseline 3 applies.

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?

States a specific verb and resource ('Reset a user password') and explicitly ties the token origin to the sibling tool auth_forgot_password. An agent can distinguish it from auth_update_profile without opening either schema.

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?

Makes the precondition clear: the tool requires a token obtained from auth_forgot_password via email. It does not explicitly exclude the other password-change sibling (auth_update_profile for logged-in users), so the when-not is only inferred.

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