put-user

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

The description adds minimal behavioral context beyond what annotations already provide ('readOnlyHint: false', 'openWorldHint: true'). It does not disclose mutation details, side effects, or authorization requirements. Potential contradiction between 'openWorldHint: true' and schema 'additionalProperties: false' is not addressed.

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 brief (one short sentence), which is concise but lacks sufficient information. It is not verbose, but it does not earn its place by providing necessary details.

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 simple input schema (3 parameters, no nested objects) and lack of output schema, the description should explain behavior (e.g., idempotency, partial updates). It fails to provide a complete picture, leaving the agent without key operational context.

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 description does not explain any of the parameters ('name', 'password', 'tags'). With 0% schema description coverage, the description should compensate but fails to add any semantic meaning beyond the schema.

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 'Create or update a user' clearly states the verb-resource combination. However, it does not distinguish this tool from sibling tools like 'set-user-limit' or other user operations, lacking specificity.

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 'hash-password' or 'set-permission'. There is no mention of prerequisites or conditions for update vs creation.

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