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

Annotations only carry readOnlyHint, so the description does the heavy lifting: deleted shifts never match, elapsed duration excludes breaks, the shorter_than_minutes boundary is exclusive (exactly 180 does not match), and pagination completes via a complete flag or next_offset that becomes stale after mutations. These are non-obvious behaviors an agent would otherwise get wrong.

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 dense paragraph, but it is front-loaded with purpose, then the bulk-change use case, then pagination and return shape. Every sentence carries operational content; the only cost is that the paging and return-value guidance runs together without visual separation.

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?

There is no output schema, and the description fully compensates: it names the return fields (shift_ids plus per-shift summary with UTC times, elapsed_minutes, user, location, role, published), the complete flag, and next_offset. Combined with the deletion caveat, an agent has everything needed to call and page this tool correctly.

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 coverage is 100%, so baseline is 3, and the description adds the critical definition that elapsed_minutes is end minus start with the break not subtracted, which the schema never states, plus a boundary example and the note that max_results aligns with delete_shifts' 100-id cap. Most remaining parameters (roles, users, locations, published) are left entirely to the schema.

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?

States a specific verb and resource with the exact filter axes (open/assigned, published, location, role, elapsed duration) and a time range, which pins down scope precisely. It implies a distinction from the other shift-listing siblings by noting it 'reads page after page', but never names rotacloud_list_shifts or rotacloud_get_shift as the non-paginated alternatives, so differentiation is inferred rather than stated.

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?

Gives a clear when-to-use rule: this is the way to select shifts for a bulk change such as rotacloud_delete_shifts, plus a concrete worked example (open shifts under 3 hours = open: true, shorter_than_minutes: 180). It also tells the agent to restart from offset 0 after a delete because positions shift. It doesn't say when a different listing tool should be used instead.

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