Get Group Members

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

With no annotations and no mention of side effects, permissions, or read-only nature, the description relies solely on the verb 'Get' to imply a safe operation. It does not explicitly disclose any behavioral traits such as whether it returns nested members or only direct members.

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, straightforward sentence with no unnecessary words. It is concise and easy to parse.

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?

While the description is adequate for a simple retrieval, it does not mention what the returned members look like, whether the result is sorted, or any edge cases (e.g., group not found). The output schema exists but is not referenced in the description.

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?

The parameter group_name is described as 'Group name or DN', which clarifies the accepted format and adds value beyond the basic schema. This is helpful for selecting the correct identifier.

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 clearly states the action ('Get') and the target ('all members of a specific group'), which distinguishes it from sibling tools like search_groups or get_person_groups. It is specific and 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?

The description provides no guidance on when to use this tool versus alternatives, such as search_groups or get_person_groups. There is no mention of use cases, prerequisites, or contrasting conditions.

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