update_user

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

No annotations provided, so description must disclose side effects. It fails to mention potential impacts (e.g., session invalidation on password change, immediate effect of role change, atomicity of updates). The 'admin only' note is helpful but incomplete.

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?

Single sentence with clear front-loaded verb and resource, followed by a concise list of fields and a critical constraint. No filler or redundant content.

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?

Tool has 4 parameters and no output schema, yet the description omits return value, error conditions, and partial update behavior. For a mutation tool with security implications, more completeness is expected to guide correct invocation.

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 descriptions cover 100% of parameters individually. The description adds value by summarizing the parameters and explicitly noting the admin restriction, which is not fully captured in the enum-less schema. This aids agent understanding beyond raw schema.

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?

Description clearly states action (update) and resource (user), specifies modifiable fields (username, password, role), and includes a restriction (admin only). This distinguishes it from sibling tools like update_team_user or update_my_password.

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 vs alternatives, no conditions or prerequisites beyond 'admin only'. Does not explain when not to use or provide context for choosing this tool over similar ones.

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