update_user_password

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

No annotations are provided, so the description must carry the behavioral burden. It does not disclose whether admin privileges are required, whether sessions are invalidated, or if the change is logged. This is a mutation tool, and the description omits critical safety information.

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 efficient sentence with no wasted words. However, it could be improved by adding usage hints while remaining concise.

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 exists, and the description omits return behavior, error conditions, or prerequisites. For a password update tool, the agent needs to know about constraints like old_password requirements, which are only hinted in the schema. The description leaves too much to inference.

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 includes descriptions for all fields ('User ID', 'New password', 'Current password (required for non-admins)'). The description adds no extra value beyond the schema, 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 clearly states 'Update a user's password in Metabase' with a specific verb ('Update'), resource ('user's password'), and context ('Metabase'). It distinguishes itself from sibling tools like 'create_user_password_reset_url' (which creates a reset URL) and 'update_user' (which likely updates other fields).

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 tool versus alternatives (e.g., 'create_user_password_reset_url' for a reset workflow). No mention of required permissions or prerequisites like needing the old password for non-admins. The tool could be misused without these cues.

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