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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that membership can be filtered by active/inactive/all and that only id and username are returned, but says nothing about pagination, result caps, or behavior when the usergroup does not exist — significant for a list endpoint.

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?

Very short, front-loaded, and every element (member fields, status options, endpoint) carries information. It borders on under-specification rather than verbosity, and the endpoint template is placed last where it helps least.

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?

With no output schema, the description does at least state the returned fields, and annotations cover the safety profile. However, for a paginated-style list tool with an undocumented required parameter, it leaves the agent without enough context on result volume or error conditions.

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 only 50%: `status` is documented in the schema (including its 'Default active.' note) and the description merely repeats the enum values. `usergroup_id` has no description in either place, and the description does not clarify that it is the group identifier path parameter, so the coverage gap is not compensated.

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 phrase 'Members of a usergroup (id and username)' names the resource and even the returned fields, and the endpoint path confirms it is a read/list operation. It is distinguishable from siblings like axislms_list_usergroups (groups, not members) and axislms_add_usergroup_member (mutation). It is a fragment rather than a full sentence, but the intent is unambiguous.

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 guidance on when to call this versus axislms_get_usergroup, axislms_list_users, or the add/remove member tools. The status option implies a filtering choice, but no conditions or prerequisites (e.g. the group must exist) are stated.

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