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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds the 'WRITE' prefix, the concrete HTTP DELETE endpoint, and the membership precondition, but says nothing about whether removal revokes derived enrollments or how errors are surfaced.

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?

Two short sentences, front-loaded with the 'WRITE:' classification so the agent sees the mutation risk immediately. The endpoint string is somewhat redundant with the tool name but does double duty as parameter documentation.

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 destructive two-parameter mutation with no output schema and 0% schema description coverage, the definition covers the action and the path binding but leaves error behavior, side effects, and return value entirely unstated. Adequate to invoke, thin for deciding consequences.

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%, so the bare integer properties carry no meaning on their own. The REST path template '/usergroups/members/{usergroup_id}/{user_id}/' documents both parameters and their roles/order, which is a real contribution, but no format or constraint detail beyond that.

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 ('remove a user from a usergroup') and adds the precondition 'they are a member of', which distinguishes it from sibling mutation tools like axislms_add_usergroup_member or axislms_create_usergroup. It does not explicitly name an alternative tool, so it falls short of a 5.

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 only usage signal is the implicit precondition that the user must already be a member. There is no guidance on when to use this versus unenrolling a user from a course/learning path, nor any statement about what happens if the membership does not exist.

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