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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. Beyond that the description discloses the payload shape (ids with start, end, and deletion time) and the underlying endpoint, which is genuinely additive given 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?

Two sentences, front-loaded with the result payload and the sync use case, with the REST path trailing harmlessly. Efficient and well ordered, with no filler, though the endpoint string is marginal information.

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 description usefully enumerates the returned fields, and pagination semantics live in the schema. What remains thin is the deletion/timezone nuance of deletion time and any guidance on large ranges, but nothing essential for a correct call is missing.

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%: the schema already documents ISO 8601 formats for start_date/end_date, pagination via page/per_page and next_page, and the location_uuid source. The description only restates "date range at a location" and adds no format or constraint detail, so 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 states a specific verb+resource with precise scope: shift ids deleted within a date range at a given location, plus the fields returned. It is clearly separable from homebase_list_shifts (live shifts) and homebase_list_deleted_timecards (different resource), though it never names a sibling explicitly.

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?

"Use it to keep a copy of the schedule in sync" gives one concrete scenario (reconciliation/sync), which implies when to reach for it. However it offers no when-not guidance and does not contrast with homebase_list_deleted_timecards or homebase_list_shifts, leaving the routing decision partly to inference.

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