set_user_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 discloses the three behavioral modes and a project-level requirement (allow_password_set=true) for passwordless users. However, it does not mention side effects like session invalidation, permission requirements beyond the access_token, or error handling. The behavioral disclosure is adequate but not exhaustive.

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 concise, with three sentences that are front-loaded and directly informative. Every sentence provides essential guidance without repetition or extraneous details.

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?

Given the tool's complexity (three modes), no output schema, and no annotations, the description covers the modes and parameter conditions well. However, it lacks information about the effect of the operation (e.g., immediate update, session invalidation) and potential errors. It is complete enough for basic usage but leaves some gaps for an AI agent.

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%, so the schema already documents parameters. The description adds significant value by explaining how the optional current_password parameter determines the mode (change vs reset/set) and by noting the project-level requirement for passwordless users. This context goes beyond the schema descriptions.

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's purpose: changing, resetting, or setting a user's password. It uses specific verbs and resource ('password'), and distinguishes three distinct modes based on parameters. Among the sibling tools, there is no other password-related tool, so differentiation is clear.

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 provides explicit instructions for each mode: for change, provide current_password + new_password; for reset, just new_password; for set (passwordless user), requires allow_password_set=true on project. This gives clear context for when to use each mode, but it does not explicitly mention when not to use the tool or alternatives.

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