Get group members

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the exact HTTP method and path, notes that there are no body fields, and provides a reference link. It does not describe return format or pagination behavior, but that is partially addressed in the query schema. The added endpoint and body-info provide some value beyond annotations.

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 extremely concise: a single sentence stating the purpose, followed by the endpoint, a note on body fields, and a reference link. Every element is essential and front-loaded with the core action. No redundant or vague phrasing.

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 read-only GET tool with annotations already covering safety and idempotency, the description is largely complete. It gives the endpoint and notes the absence of a body. The schema covers parameters well enough, and the reference link provides deeper documentation. It could mention that the response is a list of members or that pagination is available, but these are minor gaps given the annotations and schema context.

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 50%: the query parameter has a detailed description, while the path parameter (groupID) is only defined as a string with minLength. The tool description does not add any parameter semantics beyond the endpoint template, which already shows {groupID} as a path variable. It does not clarify the meaning of groupID or its expected format beyond the schema, so it does not compensate for the missing path description.

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 and resource: 'Get group members', and provides the exact HTTP endpoint for clarity. It clearly distinguishes from sibling tools like xmatters_get_a_group (fetch a single group) and xmatters_get_groups (list groups) by specifying the members sub-resource.

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 gives no guidance on when to use this tool versus alternatives. It does not mention that this is for retrieving the membership list of a specific group, nor does it contrast with related tools such as adding or removing members. Usage context is implied by the name and endpoint but not explicitly stated.

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