change_password

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely states the action without mentioning any side effects such as session invalidation, whether old_password verification is required, or if the change is irreversible. This is insufficient for a sensitive mutation operation.

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 a single, straightforward sentence with no unnecessary words. It is front-loaded and easy to parse, making it an appropriately concise formulation.

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?

For a simple tool with two fully-described parameters and no output schema, the description is merely adequate. It tells what the tool does and the schema provides the parameter details, but it omits important contextual information such as whether the action is reversible, what happens after success, or any preconditions beyond providing the old password.

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?

The input schema already describes both parameters with high coverage (100%: 'new_password' has minLength and description, 'old_password' has description). The tool description adds no additional parameter meaning, so the baseline score of 3 applies.

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 'Changes the account password' clearly identifies the action (change) and the resource (account password). It is specific and unambiguous, and it distinguishes itself from all sibling tools since no other tool appears to handle password changes.

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 usage context is implied: it is used when an account password needs to be changed. The description does not explicitly state when to use this tool versus alternatives, but given that no other sibling tool provides password-changing functionality, the implied usage is clear enough for a basic case.

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