ado_get_group_members

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

Annotations already provide readOnlyHint=true, so the description does not need to repeat that. The parameter description adds value by noting the source (from ado_list_groups), but no additional behavioral traits (e.g., pagination, response format) are disclosed. Adequate but not rich.

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?

Single sentence with 12 words, perfectly front-loaded. No redundant information. Every word earns its place.

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 simple 1-parameter read-only tool with annotations, the description is somewhat complete but lacks details about the output (list of members, fields returned, pagination). Without an output schema, the agent might need to infer what the result looks like.

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 100% and the parameter description 'Group subject descriptor (from ado_list_groups)' adds meaningful context beyond the schema type. This helps the agent know where to obtain the parameter value.

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?

Description clearly states the tool lists members of a group by subject descriptor. Verb 'List' and resource 'members of a group' are specific and distinguish from sibling tools like ado_list_groups (which lists groups) and ado_list_team_members (which lists team 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 on when to use this tool versus alternatives. The description does not mention when to use ado_list_group_members over ado_list_team_members or provide any context about prerequisites beyond the parameter hint. A clear usage context is missing.

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