change_my_password

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

No annotations are provided, so the description carries the full burden. It only states the action without disclosing whether current password verification is required, side effects like session invalidation, or any other behavioral details. This is a significant gap for a password-changing 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?

The description is a single, clear sentence with no wasted words, front-loading the action. While it is concise, it omits essential details about the parameter structure, so it is slightly under-specified for a tool with a nested object parameter.

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?

The tool has a nested object parameter and no annotations, yet the description is just one sentence. It does not explain the required structure of the password object or any relevant context, making it incomplete for an agent to use correctly despite the presence of an output schema.

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 describes a single 'password' parameter as an object with additionalProperties true, but the description does not explain what fields this object should contain (e.g., currentPassword, newPassword). With schema description coverage at 0%, the description offers minimal guidance beyond 'the password', leaving the parameter structure ambiguous.

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 the tool changes the current user's password, using a specific verb and resource. It explicitly says 'current user's', which distinguishes it from the sibling tool 'change_user_password' that likely targets other users.

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 phrase 'current user's' implies the tool is used to change one's own password, which indirectly suggests using the sibling 'change_user_password' for other users. However, there is no explicit statement of when to use it vs alternatives or when not to use it.

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