update_user_password

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

Annotations already declare destructive=true, idempotent=false, openWorld=true, so the safety profile is covered. The description adds nothing beyond the route: no statement that the old password is invalidated, no auth/permission requirements, no rate limiting or session-invalidation effects. The 'JSON-encoded string fields must remain strings' note is generic boilerplate.

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, front-loaded with the action and route. Little waste, though the trailing encoding sentence is generic filler.

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?

A destructive mutation with a nested body, zero schema descriptions, and no output schema. The description should at minimum enumerate the required body field and state the effect on the user's existing credentials; it does neither.

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% and the body is a nested object with a password property. The description only says 'supply API fields in body' without naming password as the required body field or clarifying that user_id is the target account, so it fails to compensate for the undocumented 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?

States a specific verb+resource ('Updates user password') and even the underlying route POST /users/{user_id}/password. It implicitly differentiates from the sibling update_user, though it never says so explicitly.

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 versus update_user or the TOTP/enable-disable siblings, and no prerequisites (e.g., admin rights). The only usage-adjacent content is the HTTP route and a body-format note.

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