update_user

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

The description fails to disclose any behavioral traits. It does not mention that it is a PUT request (implying full replacement of the user resource), required permissions, or effects on existing data. Since no annotations are provided, the description carries the full burden of transparency but delivers nothing.

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 short (two lines), which is concise, but it sacrifices necessary detail. It lacks structure and does not earn its place because it provides no useful information beyond the name and endpoint.

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 complexity of the input schema (nested UserBase object with many fields) and the absence of an output schema and annotations, the description is completely inadequate. It does not explain return values, side effects, or how to use the parameters 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?

The input schema has 0% description coverage, meaning no parameter descriptions are provided in the schema. The description does not add any meaning to the parameters, such as explaining what 'body' fields like 'admin', 'email', 'fullName' represent or how they are used.

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 only states 'Update User' and the endpoint URL, which is barely more than the tool name. It does not specify what aspects of a user can be updated or how it differs from other update tools like update_password or update_user_image.

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 is provided on when to use this tool versus alternatives such as update_password or update_household_preferences. There is no mention of context or prerequisites.

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