update_userUpdate a Polizei user's data by ID. Modify username, password, fullname, state, extra, or profile; profile fields merge with existing data.
Actualiza los datos de un usuario (por id). El perfil se fusiona si se envía.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID del usuario | |
| extra | No | ||
| state | No | ||
| profile | No | ||
| fullname | No | ||
| password | No | ||
| username | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
It discloses the profile merge behavior, but omits details like password handling, extra field behavior, or error cases, which would be expected without annotations.
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 concise sentences front-load the primary purpose and key behavior without redundancy.
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?
With 7 parameters including nested objects and no output schema, the description is too sparse; it omits parameter semantics, response format, and failure modes.
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?
Only 'id' is described in the schema; the description adds no explanation for extra, state, fullname, password, or username, leaving their roles 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 it updates a user's data by ID, distinguishing it from create/delete/list operations among siblings.
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?
It implies use for existing users but does not explicitly contrast with create_user or other update variants, leaving some ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.