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

Annotations already declare readOnlyHint=true, so the safety profile is covered structurally. The description adds nothing behavioral beyond restating the HTTP route — no note on whether a missing id errors, what fields the shift carries, or any access scoping.

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?

Two telegraphic fragments with zero padding, and the essential scope ('one shift') is front-loaded. It is efficient, though the endpoint restatement adds little and the style is clipped rather than polished.

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 single-parameter read tool with full schema coverage and a readOnlyHint, little else is strictly required, and there is no output schema to explain. However, with no output schema the description could usefully indicate what a shift record contains or how missing ids behave.

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% and the single shift_id parameter is fully documented in the schema. The description's 'by id' merely echoes the schema, so the baseline 3 applies.

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 ('One shift by id') and the underlying endpoint, which separates it from rotacloud_list_shifts, create_shift and update_shift. It does not name the siblings explicitly, but the singular/plural distinction is clear.

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 on when to use this versus alternatives such as rotacloud_list_shifts or rotacloud_get_user. The 'by id' phrasing implies the precondition of already knowing a shift id, but nothing states when-not-to-use or what to do without an id.

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