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

With readOnlyHint=true already declaring the safe-read profile, the description adds real value beyond annotations: it enumerates the response fields (break, location, role, notes, published and acknowledged state) and clarifies the open-shift semantics (null assigned user). It also names the underlying endpoint (GET /shifts). Pagination behavior is left to the schema fields.

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 sentences, front-loaded with the core action and scope, then the filter capabilities. Every clause carries information: the field list doubles as response documentation and there is no redundant padding.

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, so the description usefully enumerates the returned fields, and the read-only nature is covered by annotations. For a 10-parameter list tool with full schema coverage the essentials are present; only pagination/capping behavior is left entirely to the schema rather than the description.

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 description coverage is 100%, so the schema already documents all ten parameters including start/end formats, limit, offset, and filter arrays. The description restates the filter set (users, locations, roles, open, published) and Unix-seconds times but adds no syntax or constraints beyond the schema; baseline 3 is appropriate.

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 ("List rota shifts") plus the time-range scope, so an agent can immediately tell it is a read/list tool. It does not explicitly name the sibling it differs from (rotacloud_get_shift for a single shift, rotacloud_list_attendance for attendance), so differentiation is inferable 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?

"Filter by users, locations, roles, open or published" implies the narrowing use case, giving implied usage guidance. However there is no explicit when-to-use vs alternatives guidance (e.g. use this to enumerate vs get_shift for one shift) and no exclusions or prerequisites, leaving the agent to infer the context.

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