update_user

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

With no annotations, the description carries the burden of behavioral disclosure. It does disclose a significant behavioral trait: admin-only access ('Requires ADMIN'). However, it omits other important aspects like whether the update is partial (patch), what happens to missing fields, or any side effects. The admin requirement provides some transparency but it's limited.

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 extremely concise: two short sentences that are immediately clear and front-loaded. Every word adds value ('Update a user' + 'Requires ADMIN'), with no fluff or unnecessary detail.

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?

Despite the presence of an output schema, the description is incomplete for a mutation tool that accepts a free-form patch object. It doesn't specify which user fields can be updated or clarify the patch semantics. Given the tool's complexity (nested object parameter) and lack of annotations, 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?

Schema description coverage is 0% and the description adds no parameter information. It does not explain what 'user_id' and 'patch' mean, nor that 'patch' is a partial update object. The description fails to compensate for the schema's lack of detail, leaving param semantics unclear.

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 action ('Update') and the target resource ('a user'), which is specific and unambiguous. It distinguishes from sibling tools like create_user, delete_user, and get_user by indicating a modification operation.

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 no guidance on when to use this tool vs alternatives, such as create_user or change_user_password. The only usage clue is 'Requires ADMIN', which is a permission prerequisite, not an explicit usage scenario or comparison with other tools.

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