cipp_reset_password

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

Goes beyond the destructiveHint annotation by explicitly stating the password invalidation and reversibility. However, does not disclose potential side effects like session termination or permission 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, with only two sentences. The high-impact warning is front-loaded, and every word adds value without redundancy.

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?

Covers core purpose and important caveats, but omits mention of return values (e.g., whether the new password is returned) and required permissions, which would be helpful given the high-impact nature.

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?

Input schema already provides 100% description coverage for parameters. The tool description does not add significant new meaning beyond stating the operation, so a baseline score of 3 is appropriate.

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?

Description clearly identifies the tool's action: resetting a user's password and invalidating the current one. It distinguishes well from sibling tools like cipp_disable_user or cipp_revoke_sessions by focusing on password reset.

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?

Provides a clear when-not-to-use directive ('Confirm with the user before invoking'), but lacks explicit guidance on when to prefer this tool over alternatives or prerequisites, such as permissions or user existence.

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