update_user

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only lists variable names and an example. It fails to state the mutation's effect, required permissions, or any side effects, making it non-transparent.

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 a flat, unstructured dump of variable names and a truncated JSON example. It lacks a clear introductory sentence and is not front-loaded with the most useful information, appearing under-specified rather than concisely complete.

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 a 14-parameter mutation with no annotations and no output schema, this description is severely inadequate. It provides no context on return values, side effects, or required fields, leaving the agent with only a partial example and a list of parameter names.

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 100% per context, so the schema already documents each parameter. The description adds only a raw list and an example with placeholders like '<ID HERE>', but it does not clarify meanings beyond the schema, earning the baseline score.

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 'User · mutation updateUser' essentially restates the tool name and indicates it's a mutation, but provides no explicit statement of what the tool does. It does not distinguish this from sibling update tools like update_pod or update_role.

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 given on when to use this tool or how it relates to alternatives. The raw variable list and example offer no contextual usage direction.

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