get_group_members

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

With no annotations, the description carries the full burden; 'Get' implies read-only but safety/mutation profile is never asserted. It gives partial output context ('detailed member information and nesting levels') but says nothing about permissions, pagination, or behavior with large/cyclic nested groups.

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?

Front-loaded purpose line is good, but the second sentence restates it almost verbatim ('option to include nested group members'), and the trailing sentence about detailed member info is vague filler. Examples earn their place; the rest has redundancy.

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 two-param read with no output schema and no annotations, the agent still lacks the return shape (what 'detailed member information' contains) and any resolution rule against the near-duplicate get_nested_group_members sibling. Adequate but with clear gaps.

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% and both parameters are self-documented, so baseline 3 applies. The examples add a little practical clarity about what recursive=True means (nested group members) but no format or edge-case detail 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?

Specific verb + resource ('Get members of a group') with the recursion scope stated up front, and worked examples of both modes. It does not, however, distinguish itself from the sibling get_nested_group_members, which sounds like it targets the same resource.

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 examples imply when to set recursive=True vs. leave it off, so basic usage is inferable. There is no explicit when-not guidance and no routing between this tool and get_nested_group_members or get_group, which an agent will genuinely hesitate between.

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