Get members in a shift

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

Annotations already declare the tool read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds the HTTP GET method, 'Body fields: none,' and a documentation reference, but does not address response format or pagination behavior, which is left to the schema.

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?

Three short sentences with no filler: the action, the exact endpoint, the body requirement, and a reference link. Information is efficiently front-loaded.

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 operation with strong annotations, the endpoint, body requirement, and reference are largely sufficient for invocation. However, the description does not describe the expected response or clarify selection against closely related member/shift tools, so an agent is left to infer some 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?

The endpoint template maps groupID and shiftID into the path, and 'Body fields: none' clarifies there is no request body. However, the description does not explain the meaning of the path parameters beyond their self-explanatory names, and the query object's onDuty/pagination behavior is documented in the schema rather than the 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 the action and resource clearly ('Get members in a shift') and provides the full GET endpoint, making the operation unambiguous. It does not explicitly contrast with sibling tools like xmatters_get_group_members or xmatters_get_a_shift, though the shift-scoped path helps distinguish it.

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?

No guidance is provided about when to use this tool versus alternatives such as xmatters_get_group_members or the shift endpoints. The description simply restates the operation with no exclusions, prerequisites, or selection context.

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