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

With only readOnlyHint available, the description adds real behavioral context: the hard 45-day range cap, the REST endpoint, decimal hour units, and that pay rates appear only when defined. It does not discuss pagination, empty-range handling, or permission requirements.

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, front-loaded with the return content before filters and the endpoint. Every clause carries information, though the trailing endpoint reference is marginally redundant for an agent.

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 carries the burden of describing return values, and it does so thoroughly (per-user/day totals, break breakdowns, approval/submit/lock flags, pay items with rates). Combined with the stated range limit and filters, an agent has everything needed to call it correctly.

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 parameters are already fully documented in the schema. The description echoes the date-range limit and filter dimensions but adds no syntax or value semantics beyond what the schema provides; a 3 baseline 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 (get) and resource (timesheet totals of a time clock) with scope and content: per-user/per-day hours, flags and pay items. It is clearly distinguishable from siblings like connecteam_list_time_activities or connecteam_list_time_clocks, which are named/implied elsewhere.

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?

Conveys when the tool applies (payroll-ready totals for a time clock over a date range) and what can be filtered (users, groups, jobs, approval state). It does not explicitly name an alternative tool or state when not to use it, so it falls short of a 5.

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