Add a member to a shift

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

The description adds meaningful side-effect context beyond the annotations: it requires operator write opt-in, confirm:true, and warns that it may notify recipients or change tenant data. This aligns with destructiveHint=true and provides useful behavioral expectations.

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 compact and front-loaded with the core action, then supplies the endpoint, key body fields, requirements, and a reference link. It avoids unnecessary prose, though the opening sentence largely restates the tool title.

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?

The description gives enough to attempt the call: endpoint, path parameters, body field names, confirm requirement, and side-effect warnings. Still, it lacks details on required body fields, response shape, and error cases, which are important for a destructive, open-world mutation with no output schema.

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 description lists body fields (recipient, position, delay, escalationType, inRotation, onDuty), which adds value because the schema only defines body as an arbitrary JSON payload. However, it does not explain the meaning, types, or allowed values of these fields, leaving important semantics to the external reference.

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 clearly states the operation as 'Add a member to a shift' and reinforces it with the exact REST endpoint POST /api/xm/1/groups/{groupID}/shifts/{shiftID}/members. This distinguishes it from siblings like xmatters_add_a_member_to_the_group and xmatters_get_members_in_a_shift.

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 given about when to choose this tool over alternatives, such as adding a member to a group or retrieving shift members first. The description focuses on how to invoke the API but not on the decision context.

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