customer_change_password

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

No annotations exist, so description carries the full burden. It notes passwords are plain text but never logged, and confirm_new_password must match. However, it lacks disclosure of success/failure behavior, side effects (e.g., notification), or security implications beyond logging.

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 concise with a clear structure: a one-line purpose followed by a parameter list. Every sentence adds value. No redundant 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?

Output schema exists, so return values need not be explained. The description covers parameter semantics and security notes. Missing prerequisites (e.g., customer must exist) and validation rules (e.g., password strength). Adequate but could be more 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 description coverage is 0%, so the description compensates by explaining each parameter: email, old_password with 'never logged', new_password with 'never logged', confirm_new_password with 'must match'. This adds significant meaning beyond the bare 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 'Change a customer's password.' with a specific verb and resource. It distinguishes from siblings like customer_password_recovery and customer_update by focusing on direct password change with old password verification.

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 implies when to use (customer wants to change password knowing current password) but does not explicitly state when not to use or mention alternatives like customer_password_recovery for forgotten passwords. The agent may need more guidance.

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