set_user_password

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

Describes the three modes and parameter conditions, but lacks details on side effects (e.g., token invalidation), error cases, or necessary prerequisites beyond access_token and project settings.

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 sentences with no fluff; the first sentence states the core purpose, followed by concise mode-specific details. Efficient and well-structured.

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?

Adequately explains the modes, but omits expected outcomes, error handling, and behavioral nuances like session invalidation. For a sensitive tool, more completeness would be beneficial.

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?

Adds significant meaning beyond the schema by explaining the conditional requirement of current_password and the role of new_password. The schema already covers all parameters clearly.

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 three distinct operations (change, reset, set) with specific parameter requirements, making it unambiguous and distinguishable from sibling tools like create_auth_user.

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?

Explicitly explains when to use each mode (change requires current_password, reset via magic link, set requires allow_password_set=true), but does not mention alternative tools or scenarios to avoid.

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