directory_list_group_members

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds valuable behavioral context: the required permission (GroupMember.Read.All), the exclusion of nested group members, and the specific return fields (name, email, job title, department, total count). No contradiction with annotations.

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?

Three concise sentences, each adding value: purpose and source, return payload, use case and limitations/permission. No redundancy or filler. Front-loaded with the primary action.

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 list tool with no output schema, the description covers the input source, output fields, total count, permission requirement, and membership scope limitation. It is sufficiently complete for an agent to select and invoke the tool correctly, and annotations cover safety and idempotency.

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 covers both parameters with descriptions (group_id as Entra group ID, max_results with range). The description adds practical guidance by specifying the source for group_id (directory_search_groups) and implies max_results is for limiting output. This exceeds the schema baseline of 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 clearly states the tool's function: 'List the people in an Entra ID group' with a specific resource (group members) and input source (group id from directory_search_groups). It distinguishes from sibling tools like directory_search_groups (search) and directory_get_group (group info) by specifying it returns member details and total count.

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?

Provides a clear prerequisite ('given a group id from directory_search_groups') and an example use case ('who is on the claims team'). It also states a limitation ('Only direct members are listed') that helps decide when to use. However, it does not explicitly name alternative tools for cases like nested group membership.

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