Get Groups Members By Username Or

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

With no annotations, the description carries the burden and does reveal that this is a read operation returning exactly one user scoped to the current group. It does not disclose authentication requirements, not-found behavior, or what happens if the username_or_id does not belong to the group.

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 one front-loaded sentence with no filler and starts with the operation. It is concise, though the brevity omits the lookup criterion that would make it more 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?

Although an output schema exists, the definition is incomplete for an agent: the required username_or_id parameter is effectively undocumented and 'current group' semantics are unexplained. An agent cannot reliably know what value to pass or when this endpoint applies.

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%, and the description adds almost no parameter-level meaning. It implies the result is a group member, which weakly relates to username_or_id, but it never explains that the parameter accepts a username or UUID, nor what accept-language controls.

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 names a clear action ('Returns') and resource ('a single user belonging to the current group'), and its singular scope distinguishes it from list_groups_members. It does not explicitly state that the user is selected by username_or_id, leaving that key detail to the tool name and parameter.

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 about when to use this tool instead of list_groups_members or other membership endpoints, and no exclusions or prerequisites are given. The phrase 'current group' implies a context, but it does not explain how an agent should choose this tool.

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