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

Annotations already declare readOnly/openWorld/non-destructive, so the bar is lower, yet the description adds real value: results are returned oldest-first, each shift carries the alerts ClockShark raised (e.g. a missing clock out), and it needs a Cotlet API key with access to this app. Ordering and auth requirements are behavioral traits not in the annotations.

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?

Front-loads purpose and return shape before the filtering and downstream-use sentences. Dense but nearly every clause earns its place; the 'Shifts from Time > View' preamble is slightly UI-flavored but still orienting.

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 contract itself (fields, oldest-first ordering, embedded alerts) and also covers filtering, auth, and how the IDs feed downstream edit/approve tools. Nothing an agent needs to call it correctly is missing.

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 from/to, employee_ids, approval_status auto, and with_alerts_only are already fully documented. The description restates the filtering intent without adding format or default detail 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 and resource (list time entries/shifts) and enumerates the returned fields (employee, job, task, start, end, breaks, notes, alerts, approval status). An agent can tell it apart from siblings like clockshark_list_shifts or clockshark_list_clocked_in by the date-range shift semantics described.

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?

Gives concrete conditions for filtering (by employee, by approval status, alerts-only) and explicitly routes the agent forward: 'Use entry_id and employee_id from here in the edit and approve tools.' It does not, however, contrast itself against the nearby clockshark_list_shifts sibling, so the when-not guidance is incomplete.

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