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. The description adds genuinely non-obvious behavioral data: that time-off hours are always 0 on timecards, and which fields each record carries. It does not discuss result ordering or pagination semantics, which the schema handles instead.

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 dense sentences plus the endpoint path, all front-loaded: resource and scope first, then the field inventory, then the time-off caveat and alternative. No filler or repetition.

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 returned fields (employee, role, clock in/out, breaks, hours, labor cost, tips, approval state) and warns about the time-off=0 trap. Pagination is covered by the schema, so the remaining gap is minor (no ordering or volume expectations).

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 (including the date_filter enum and the page/per_page follow-the-next_page instruction) is already documented in structured data. The description restates the date-range scoping but adds no syntax, defaults, or constraints beyond the schema, so 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 (List), resource (timecards), and scope (a location, in a date range), then enumerates what each record contains. It is clearly distinguishable from homebase_get_timecard (single record) and homebase_list_deleted_timecards by its 'worked time' framing and the API path GET /locations/{location_uuid}/timecards.

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?

Explicitly routes one case away from this tool: 'Time-off hours are always 0 on timecards; use homebase_get_labor_by_employee for totals with time off.' That is a real alternative with a stated condition. It stops short of when-not-to-use guidance against other siblings (get_timecard, list_deleted_timecards) and says nothing about pagination as a usage pattern.

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