change_password

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

No annotations are provided, so the description carries the full behavioral burden. It notes the authentication requirement but says nothing about whether other sessions/tokens are invalidated, what happens on an incorrect current_password, or whether the change is reversible — all material for a credential mutation.

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?

Front-loads the action in one line, then lists args compactly with no filler. The preamble 'Requires authentication' before the args block is slightly awkward placement but still earns its place.

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?

An output schema exists so return values need no explanation, but for an unannotated, security-sensitive mutation the description omits session invalidation behavior and failure modes. An agent could invoke it correctly, but not with confidence about side effects.

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 must compensate, and it does not. The 'Args' lines ('current_password: Current password') merely restate the property titles, adding no format, length, or validation semantics.

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 ('Change account password'), which is unambiguous on its own. However, it draws no distinction from the closely related sibling send_password_reset, so an agent cannot tell which flow this belongs to from the description alone.

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?

'Requires authentication' gives a prerequisite, which is more than most siblings offer. But there is no when-to-use guidance versus send_password_reset (forgot-password flow) or update_profile, leaving the choosing to inference.

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