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

Annotations declare destructiveHint=true, and the description reinforces that by disclosing the REPLACE semantics for tags and the partial-update semantics (only passed fields are sent). It goes beyond the annotation by warning about data-loss-adjacent behavior, though it says nothing about permissions, validation errors, or the response.

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?

Front-loaded with the operation type, followed by scope, then the replacement caveat and sibling pointer, ending with the underlying endpoint. Every sentence adds a distinct fact; nothing is padding.

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?

For a 6-parameter mutation tool with no output schema, the description covers partial-update semantics, the destructive tag behavior, and tool routing. The remaining gap is that it never says what a successful call returns or whether the user identifier accepts email, though the schema handles the latter.

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 50%, so the description must carry some load: it assigns meaning to username, email and marketing consent, which have no schema descriptions, and clarifies that tags is a wholesale replacement. The nested fields object and tag list are already well documented in the schema, so part of the description is redundant with it.

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?

Opens with an explicit 'WRITE' verb and names the resource plus the exact updatable fields (email, username, marketing consent, sign-up fields, tags). It also names the sibling it is not (learnworlds_update_user_tags), so the agent can separate it from tag-editing tools without opening a schema.

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?

States the operating condition ('Only the fields you pass are sent') and gives an explicit routing rule: passing tags REPLACES the list, so use learnworlds_update_user_tags to add/remove individual tags. That is a clear when-to-use-this vs when-to-use-the-alternative statement.

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