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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the 'WRITE:' prefix adds little. What does add value is the membership precondition and the note that groups drive course/path assignments, hinting at downstream effects. It still omits what happens on failure (e.g., error when already a member) and whether assignment propagates immediately.

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?

Four compact clauses, front-loaded with the write nature and the precondition, with no filler. The trailing raw endpoint is slightly redundant with the name but does document the resource shape.

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 two-required-parameter mutation with no output schema and adequate annotations, the essentials are covered: operation, precondition, and endpoint. It is silent on return value or failure behavior, which leaves a modest gap for an agent chaining calls.

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 0% for both parameters, so the schema supplies only types. The description partially compensates by naming both parameters in the endpoint template (POST /usergroups/members/{usergroup_id}/{user_id}/), clarifying the path ordering, but gives no ID format or source guidance.

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 a user to a usergroup') and the parenthetical precondition clarifies the exact operation. It is trivially distinguishable from axislms_remove_usergroup_member and axislms_list_usergroup_members without opening any 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?

The precondition 'they must not already be a member' gives a real when-to-use constraint, and 'Groups can drive course or path assignments' hints at why one would do this. However, there is no routing to alternatives such as axislms_enroll_user_in_course or axislms_list_usergroup_members (to verify membership first), so usage is only implied.

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