Change the current user's password

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

Annotations indicate destructiveHint=true and readOnlyHint=false. The description adds valuable context: 'rotates the credential the current session signs in with' and 'Passwords are never logged or echoed back.' This goes beyond annotations, but could mention immediate effect on the session.

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?

Two sentences, front-loaded with purpose, no waste. Every sentence adds necessary 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?

No output schema, but description hints at no logging. For a mutation tool, typical return is success. It covers prerequisites and safety. Minor gap: does not specify what the response includes (e.g., success message).

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% with detailed descriptions for each parameter. The description adds context about 'confirm=true' being required and password sensitivity, but this mostly reinforces the schema. Baseline 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?

The description clearly states 'Change the authenticated user's password', specifying it affects the current user. This is distinct from sibling tools like describe_resource or execute_query, which serve different purposes. The title reinforces the purpose.

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 explicitly requires 'admin writes enabled (PORTAL_ALLOW_ADMIN_WRITES=1) and confirm=true', providing clear conditions for use. It does not offer alternatives or explicitly state when not to use, but the conditions are sufficient.

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