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

With readOnlyHint=true already covering the safety profile, the description still adds real behavioral context: it discloses the V1 endpoint returning one row per assigned user (an important shape quirk given no output schema), names the upstream route, and enumerates the returned fields. Pagination semantics live in the schema rather than here, which keeps it short of a 5.

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?

Front-loads purpose and scope, then the returned-field inventory, then filtering, then the endpoint. Dense but nearly every clause carries information; the long field enumeration is justified by the absence of an output 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?

For a 13-parameter read tool with full schema coverage and no output schema, the description supplies the missing pieces: scope, row granularity, returned fields, and filter dimensions. Only pagination behavior and any rate/failure notes are left implicit.

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 one of the 13 parameters is already documented, including formats, bounds, and defaults. The description restates four filter categories (assigned users, job, open, published) without adding syntax, constraints, or interaction rules beyond the schema. 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 with explicit scope: 'List shifts of one scheduler in a time window'. The parenthetical 'one row per assigned user' pins down the granularity, which is what separates this from connecteam_get_shift, and the enumerated returned fields make the tool's output identity unmistakable.

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?

The filters sentence ('Filter by assigned users, job, open or published') implies when the tool is useful for narrowing a range, but there is no explicit when-to-use vs connecteam_get_shift and no stated conditions or exclusions. Usage is inferable from context but never spelled out.

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