Update superuser

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

With no annotations provided, the description carries the burden of behavioral disclosure. It usefully discloses that changing the password requires both 'password' and 'passwordConfirm' in data, but it does not mention permissions, response shape, partial-update behavior, or whether changes are immediately effective.

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?

Two short sentences with no filler. The main purpose is front-loaded, and the second sentence adds an important edge-case instruction. Every word earns its place.

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 two-parameter update operation, the description covers the core calling requirements: id, data, and the special password-pairing rule. It does not describe return values or permissions, but given the absence of an output schema, it still provides enough context for a competent agent to invoke the tool correctly.

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 coverage is 100%, so the baseline is 3. The description adds value beyond the schema by explaining that 'data' can contain email or password fields and by highlighting the non-obvious constraint that password changes require both password and passwordConfirm together.

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 starts with a specific verb and resource, 'Update a superuser account,' and gives concrete examples of change email and reset password. This clearly distinguishes it from sibling tools like create_superuser, delete_superuser, and list_superusers.

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 implies when to use the tool: when updating an existing superuser account. However, it does not explicitly contrast it with related flows such as request_password_reset or confirm_email_change, so an agent could confuse a direct password reset with an email-based reset flow.

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