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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description usefully adds the underlying endpoint (GET /public-api/v1/clockings/) and paging behavior, but says nothing about result ordering, page size, or whether multiple filters combine as AND.

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 what the tool returns and followed by the one operational note that matters (paging). No filler. The phrasing 'pass next_page as page' is slightly awkward but not wasteful.

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 return-shape burden and does so by listing the event kinds and attributes an agent will get back, including workplace and location that are not filter parameters. Remaining gaps – ordering, page size, filter combination semantics – are minor rather than blocking.

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% and each of the 8 parameters is individually documented with type, enum, format and cross-reference. The description recapitulates the filterable fields (method values, employee, timestamps) but adds no syntax or constraint detail beyond the schema, so the baseline of 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 definition opens with a specific verb+resource ('List time-clock events') and enumerates the event kinds and returned attributes (employee, timestamp, method, workplace, location). This makes it impossible to confuse with the other list_* siblings such as list_employees or list_absence_requests.

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 only guidance is 'Paged: pass next_page as page', which covers pagination mechanics. There is no statement of when to reach for this tool versus other listing endpoints, nor of any preconditions (e.g. that an employee uuid comes from jethr_list_employees – that hint lives in the schema, not the description).

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