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

readOnlyHint=true already establishes this is a safe read, and the description usefully adds the shape of the returned data (hours, approval state). However, it says nothing about pagination, result limits, or default time-window behavior — meaningful gaps for a timesheet list endpoint.

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 compact sentences plus the upstream endpoint reference; the returned-data summary is front-loaded and every clause carries information. No filler.

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 does well to summarize the returned fields, and the annotations cover the safety profile. It falls short only on pagination/limit and default-window behavior that an agent would need for a list endpoint.

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 all five parameters including only_open are already documented in the schema. The description only echoes only_open's meaning and adds no syntax, format, or interaction detail beyond that baseline.

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 and resource ('List clocked time entries') and immediately enumerates what the resource contains — hours worked, clock-in/out, length, approval state. This is clearly distinguishable from sibling listing tools such as wheniwork_list_shifts (scheduled) and wheniwork_list_users.

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 'Use only_open to see who is clocked in right now' line gives an in-tool usage cue, but it is effectively a restatement of the parameter rather than guidance on when to choose this tool over an alternative. No when-not conditions or sibling routing are provided.

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