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

Annotations already declare readOnlyHint=true, destructiveHint=false, so the safety profile is covered. The description adds real value beyond them by inventorying exactly what each shift record contains (wage rate, regular/overtime scheduled hours, published state) and naming the GET endpoint, which matters since there is no output schema.

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?

A single front-loaded sentence that names the verb and resource first and then the returned fields, with the endpoint appended. Dense but every clause contributes; the colon-delimited field list is slightly run-on.

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, the field inventory substitutes well for a return-value contract, and the endpoint plus annotations round out the operational picture. Pagination behavior lives in the schema, so nothing critical is missing, though an explicit note on the deleted-shift sibling would complete it.

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 all eight parameters (including open, date_filter, page, per_page, with_note) are already documented in the schema. The description adds only the 'filter open shifts only' hint, which the schema already states; baseline 3 is correct when the schema carries the parameter burden.

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+resource ('List the scheduled shifts of a location in a date range') and enumerates the returned data (employee, role, department, start/end, published/open state, wage rate, labor hours). It implicitly separates itself from sibling tools like homebase_list_deleted_shifts and homebase_get_shift, but never names an alternative to make the distinction explicit.

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 one filtering behavior available ('Filter open shifts only'), which maps to the `open` parameter, but gives no guidance on when to choose this tool over homebase_get_shift (single shift) or homebase_list_deleted_shifts. Usage is implied by the resource scope rather than stated.

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