list_group_members

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

Without annotations, the description mentions member types but does not disclose behavioral traits like pagination (top parameter with default 100), filtering effects, or that 'list all' might be limited by the top parameter. Some behavioral context is implied but incomplete.

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?

One sentence, no redundancy. However, it could be more informative about optional parameters and behaviors without adding much length.

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?

No output schema exists, so description should explain return values; it does not. Also, it omits pagination details and user guidance on using optional parameters effectively.

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%, so baseline is 3. The description does not add meaning beyond the schema; it only restates groupId indirectly. No additional parameter semantics are provided.

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 lists members of a Microsoft 365 group, specifying the types of members (users, contacts, etc.), and implicitly distinguishes from sibling tools like list_tasks or list_buckets by focusing on group members.

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 vs alternatives, prerequisites (e.g., groupId), or typical use cases. It lacks explicit context such as 'Use when you need all members of a group'.

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