get_user_groups

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

With no annotations, the description carries the full behavioral burden. It discloses that detailed membership information is returned, including group types, scopes, and descriptions, but does not clarify whether this includes only direct membership or also nested/transitive groups, nor does it mention permissions, pagination, or account-scope constraints.

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?

The description is short and front-loads the core purpose, followed by useful detail and an example. The final sentence, 'Returns comprehensive group membership analysis,' is vague and does not earn its place, but overall the structure is efficient.

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 one-parameter read operation, the description is mostly adequate and explains the type of data returned. However, without annotations or an output schema, it should resolve whether nested membership is included, especially given the sibling get_nested_group_members tool.

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?

There is only one parameter, and its schema description coverage is 100%, so the schema already defines 'username' fully. The description's example adds a concrete usage form but does not significantly extend parameter semantics beyond the schema.

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 description states a specific verb and resource: getting the groups a user belongs to. It is clear on its own, but it does not explicitly distinguish itself from the inverse sibling get_group_members or from get_nested_group_members.

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 description gives an example invocation but no guidance on when to use this tool versus alternatives like get_group_members (group-to-user lookup) or get_nested_group_members (nested membership). The agent must infer the appropriate use case.

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