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

readOnlyHint=true already tells the agent this is a safe read, and the description adds the 62-day window limit and the underlying endpoint (GET /rosters). It does not spell out pagination behavior in prose, but the schema's limit/offset descriptions carry that load, so the incremental value is real if not exhaustive.

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: the first front-loads the core purpose and the 62-day constraint, the second carries the field list and the sibling hand-off. Nothing is repeated and no sentence is filler.

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 no output schema present, the description compensates by enumerating the returned fields (date, times, break, employee, team, shift type, department, published state, hours, cost) and by flagging occurrence_id as the key for follow-up calls. Combined with annotations and a fully described input schema, an agent has what it needs to call and chain 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 description coverage is 100%, so every parameter (limit, offset, user_id, min_date, max_date, department_id) is already documented with its filter meaning. The description's only added parameter-level meaning is restating the ≤62-day relationship between min_date and max_date, which the schema already expresses, 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?

The description gives a specific verb and resource and even defines the domain term ("rosters = shifts assigned to employees"), which implicitly separates it from unassigned siblings like shiftbase_list_open_shifts or shiftbase_list_timesheets. It also enumerates the returned fields, so an agent knows exactly what this call yields without opening a schema.

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?

It states the hard operating condition (date range of at most 62 days) and explicitly routes follow-up work by saying each occurrence_id is what shiftbase_get_roster and shiftbase_update_roster consume. It does not, however, state when to prefer this over adjacent list tools such as list_timesheets or list_open_shifts, so an explicit exclusion is missing.

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