get_group_members

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

No annotations are provided, so the description carries the full burden. It implies a read of the current group's members but never states pagination behavior, auth/scope requirements, or the return shape, which matters for a 7-parameter listing endpoint.

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?

The useful content is two short clauses; the rest is a ~40-term keyword dump ('list member, list members, search member...') that adds no meaning. Purpose is front-loaded, but the bulk is noise.

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 paginated list tool with 7 undocumented params, no annotations, and no output schema, the description omits pagination/ordering guidance and any scoping caveats. An agent could call it, but not well.

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% across 7 parameters (page, perPage, orderBy, queryFilter, etc.), and the description says nothing about pagination, ordering, or filtering semantics. This is the case where the description must compensate and it does not.

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 states a specific verb+resource ('List members') and adds the endpoint and scope ('Returns all users belonging to the current group'). It does not, however, distinguish itself from the near-identical sibling get_group_member or get_household_members, leaving the agent to guess which member-list tool applies.

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?

There is no when-to-use guidance, no prerequisites, and no naming of alternatives. 'Groups: Self Service' reads as a category tag rather than a usage condition, so the agent gets no routing signal versus get_group_member or get_household_members.

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