Update user resource.

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

The description adds a single behavioral constraint (authentication requirement) but does not disclose update semantics, such as partial versus full replacement, side effects, or reversibility. The annotations (openWorldHint, idempotentHint) provide some context, but the description offers minimal additional insight.

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 brief, but it is under-specified rather than concise. It contains a single clause that conveys very little, failing to earn its place by providing essential information about the tool's purpose or usage.

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 (8 parameters, no output schema, low schema coverage), the description is drastically incomplete. It does not explain what fields can be updated, what the response is, or how authentication affects invocation. An agent cannot reliably select or use this tool based on the provided description.

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 only 25% (username gets a misleading description). The description does not compensate by explaining any parameters, despite 8 parameters being present. The agent gets no help understanding required fields, formats, or relationships between fields.

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 does not state what the tool does. It only says 'This can only be done by the logged in user,' which is a constraint, not a purpose. The tool's name and title indicate it updates a user, but the description itself fails to convey the 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 implies that the user must be logged in to perform the update, but it provides no guidance on when to use this tool versus alternatives like delete_user or get_user_by_name. No exclusions or comparisons to sibling tools are given.

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