signupgenius_list_group_members

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-access profile are covered. The description adds the useful detail of what is returned (name, email, memberid), but says nothing about pagination, ordering, or authorization scope.

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?

A single front-loaded sentence with the resource first and the return payload parenthetically appended. Every clause earns its place; no filler.

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 2-param read-only list tool whose annotations carry the safety profile and which has no output schema, the description does convey the return fields. However, it omits any mention of result ordering or the meaning of the sort parameter, leaving an agent under-informed about output shape.

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 only 50%: groupId is documented in the schema ('Group ID returned by signupgenius_list_groups'), but the sort enum has no description in either the schema or the tool description. The description contributes nothing about parameters, so it fails to compensate for the coverage gap.

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 a specific verb and resource ('List members of a SignUpGenius group') and names the returned fields, which separates it from siblings like get_group_member (singular) and add_group_member. It is clear and specific though it does not explicitly name the alternative listing tools.

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?

The action 'list members of a group' implies when to use it, but there is no explicit when/when-not guidance nor any reference to the sibling get_group_member for a single member or list_groups for the group list. Usage is left to inference.

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