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

Annotations cover readOnlyHint=true, so the safety profile is set. The description adds real behavioral context beyond annotations: the 31-day cap per call, grouping by user, the specific fields emitted (start/end, job, sub-job, notes, auto clock-out), and the underlying REST route. It doesn't discuss pagination or whether users removed from a clock appear, but the 31-day rule is a meaningful operational disclosure.

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, front-loaded sentences that pack the noun phrase (what it returns), the cardinality constraint, grouping semantics, and the route. Slightly overloaded with parenthetical field lists, but every clause carries 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?

For a read-only list tool with a fully documented schema and no output schema, the description supplies the one thing the schema cannot: the 31-day cap and grouped-by-user shape. Return-value detail is absent but acceptable for a listing endpoint; pagination behavior would have pushed it to 5.

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 coverage is 100%, so the schema documents all six parameters including the date pattern and filter semantics. The description restates filters ('by users, jobs or activity type') and the date-range constraint without adding format or edge-case detail beyond the schema, making the baseline 3 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 resource (clock-in/clock-out records of a time clock) with a precise scope (date range, grouped by user) and enumerates the record types returned. Clearly distinguishable from siblings like connecteam_list_shifts and connecteam_get_timesheet_totals by naming the time-clock activity domain directly.

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 31-day-per-call limit is stated, which is a usage constraint, and the description notes filtering options. However, it never says when to choose this tool over alternatives such as connecteam_list_shifts (a very close sibling) or connecteam_get_timesheet_totals, so the agent must infer the boundary between aggregate totals and raw activity records.

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