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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the useful behavioral detail that the result merges two populations (assignees and applicants), but says nothing about ordering, pagination, or what an empty result means.

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?

One front-loaded sentence gives the payload content first, followed by the endpoint as a compact hint. Nothing is padded, though the raw REST path is mild noise for an agent that already has the schema.

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?

With one simple parameter, rich annotations, and no output schema, the description does the important remaining work by describing what the response contains (assignees and applicants with id and name). It stops short of explaining the shape of the returned collection or how to tell assignees from applicants.

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?

There is a single required parameter with 100% schema description coverage, so the schema already carries the semantics ('Papershift shift id.', positive integer). The description only echoes it via the endpoint pattern '?shift_id=', adding no format hints or edge-case guidance beyond that.

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 result set: users assigned to a shift plus users who applied, including which fields come back (user id and name). It is clearly a read of assignments for one shift, distinct in intent from papershift_assign_user_to_shift, though it never names that sibling explicitly.

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?

Usage is only implied: the required shift_id and the embedded 'GET /assignments?shift_id=' suggest 'call this when you have a shift id and want its participants.' There is no explicit when-to-use, no mention of papershift_list_shifts or papershift_get_shift as alternatives for adjacent needs.

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