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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the returned fields (id, name) and the underlying endpoint, which is useful given there is no output schema, but it says nothing about pagination, empty-result behavior, or error cases such as an unknown user id.

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 terse fragments with zero padding, and the resource scope is front-loaded before the endpoint detail. A leading verb ('Lists…') would make it read as a description rather than a label, but nothing needs to be cut.

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 single-parameter read tool with readOnlyHint set and no output schema, the description covers scope, the return shape (id, name), and the backing endpoint. There is no material gap an agent would need before calling it correctly.

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 100% for the single required user_id, so the schema already documents the type, positivity, and meaning. The description adds nothing beyond confirming the user scope in the endpoint path template; baseline 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?

The fragment 'the groups a user belongs to' states the resource and the scope (a single user) well enough to distinguish it from sibling list_groups (all groups) and list_group_users (members of a group). It is a noun phrase rather than a verb phrase, so the action is only implied, but the resource and filter are 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?

Usage is implied by the scoping ('a user') rather than stated: an agent can infer this is the right tool when it has a user id and wants that user's group memberships. There is no explicit exclusion or pointer to the related write tool (add_user_to_group) or the inverse listing, so the routing must be derived by the caller.

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