group_members

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real behavioral value beyond that: max_results is described as a page bound with a default of 200, and truncation is explicitly 'measured rather than guessed', which tells the agent how pagination state can be trusted.

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-loads the purpose, then separates Args and Returns in a compact structure with no filler. The prose is tight, though the fragment 'Members of one group, normalized user rows' is slightly terse for an action statement.

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?

There is no output schema, and the description compensates by describing the return shape (members, returned, limit, truncated). All three parameters are documented and pagination behavior is explained, leaving only minor ambiguity about what 'normalized' user rows contain.

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 0% (titles only), so the description carries the burden and does so: group_id's source, max_results' role as a page bound and default, and target as an IdP target name from config with omission meaning the default. This meaningfully supplements bare titles like 'Target' and 'Max Results'.

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?

States the specific resource and scope: members of a single group, returned as normalized user rows, with an explicit [READ] marker. It clearly differs from list_groups (which yields the group list) and list_users (which yields users, not memberships), though it never names those siblings directly.

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?

Gives clear invocation context by specifying that group_id comes 'from list_groups', establishing the prerequisite workflow step. It does not state exclusions or contrast against alternatives such as list_users, so it stops short of full when/when-not guidance.

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