signupgenius_list_group_members

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

The readOnlyHint annotation already marks this as a safe read operation, and the description's 'List' is consistent with that. The description adds useful context by specifying the returned fields ('name, email, memberid'), which is not present in the schema. No contradictions.

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 description is a single sentence that front-loads the action and resource, contains no filler, and effectively conveys the tool's purpose and return content.

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 list tool with one required parameter and a readOnly annotation, the description adequately covers the action, resource, and return fields. It omits sort/pagination behavior, but the schema documents sort and the operation is low-complexity, so the lack of extra detail is acceptable.

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?

The schema already documents groupId with a reference to signupgenius_list_groups and sort with an enum, covering 50% of parameters with descriptions. The description adds minimal parameter-level meaning beyond reinforcing that groupId refers to a group, so the schema carries most of the semantic load.

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 uses the specific verb 'List' with the resource 'members of a SignUpGenius group' and indicates the basic fields returned (name, email, memberid). This clearly distinguishes it from sibling signupgenius_get_group_member, which targets a single member.

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 description provides a clear use case: when you need to list members of a group. It does not explicitly mention alternatives or exclusions, but the context is unambiguous and directly implies when to invoke this tool.

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