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

Annotations already declare destructiveHint=true, so the safety profile is covered. The description adds genuinely useful context that the action 'may enroll them in the group's products', disclosing an indirect side effect. It still omits whether the call is idempotent if the user is already a member and what permissions are required.

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?

A single front-loaded sentence with the WRITE marker, the action, the side-effect caveat, and the endpoint path. No waste, though the raw HTTP path adds limited value to an agent over the operation name.

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 simple two-parameter mutation with full schema coverage and a destructive annotation, the essentials are present: write semantics, indirect enrollment effect, and endpoint. Remaining gaps (idempotency on repeat calls, auth scope) are minor but not fully addressed.

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%, so both parameters (group_id, user) are already well documented in the schema. The description adds no syntax or format detail beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource ('add an existing user to a user group') and the 'existing user' qualifier implicitly distinguishes it from learnworlds_create_user. However, it never names or contrasts with the closest sibling, learnworlds_enroll_user, which also performs enrollment-style actions.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named despite relevant siblings like enroll_user and create_user. Usage must be inferred from the phrase 'existing user' and the parenthetical about the group's products.

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