get_user_groups_api_v1_users_groups_get

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

No annotations are present, and the description does not disclose any behavioral traits such as whether the tool returns full group objects, pagination behavior, authentication requirements, or scope of groups (e.g., groups the current user is a member of).

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 a single, very short sentence. It is under-specified rather than concise, lacking necessary details to be useful.

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?

Without an output schema, annotations, or parameter details, the description should provide more context about return values and scope. It does not, making it incomplete for an agent to understand the tool's exact behavior.

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 are zero parameters, and schema coverage is 100%. The description adds no meaning beyond the schema; it could clarify what groups are returned (e.g., groups for the session user). Baseline for zero params is 4, but the lack of additional context reduces it to 3.

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 'Get User Groups', specifying the verb 'get' and resource 'user groups'. However, it does not clarify whether these are groups for the current user or all groups, and it fails to differentiate from siblings like 'get_groups' and 'get_user_groups_by_id'.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling tools for groups, users, and channels, the description offers no context to help choose.

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