List logged time entries

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

Annotations already mark the operation readOnly, and the description adds useful behavior: defaults to today, returns a total, and shows times in local time. This goes beyond the structured data meaningfully.

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?

Three short sentences with no filler. The action, default range, and display behavior are presented directly and front-loaded.

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 simple read-only listing tool with all optional parameters and no output schema, the description covers the key facts: scope, defaults, total, and local time. Minor gap: the format for start/end strings is not described, but the schema already provides string type and parameter purposes.

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 parameter is already documented. The tool description does not add extra parameter-level meaning beyond the existing 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?

The description uses a specific verb and resource: 'List your Clockify time entries for a period, with a total.' It clearly distinguishes this tool from sibling list_* tools (tags, projects, tasks) and timer-related tools (current_timer, log_time).

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 description provides clear context: use this tool when you need to view logged time entries over a period. It does not explicitly name alternatives or exclusion conditions, but the resource ('time entries') is obvious against siblings like current_timer or list_projects.

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