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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered; the description adds real behavioral context on top: newest-first ordering, the default user scope, and the field set returned (id, description, project, task, tags, billable, timeInterval with ISO 8601 duration). It does not mention pagination semantics or rate limits, but it goes beyond restating 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?

Three compact sentences with no filler: scope and ordering first, then filter dimensions, then the alternative tool, then the endpoint. Each sentence carries distinct information and nothing is repeated from the schema.

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 11 optional params, no output schema and no required fields, the description compensates well by listing the returned fields, stating the default user/workspace scope and ordering, and routing totals to a sibling. Nothing an agent needs in order to call this 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 description coverage is 100%, so every one of the 11 parameters is already documented in the schema, including the admin/manager role note on user_id and the next_page hint on page. The description only summarizes the filterable dimensions ('time range, project, task, tags or description') without adding format or syntax detail, so the baseline 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?

States a specific verb and resource ('List the time entries of one user'), names the default scope (you), and specifies the ordering (newest first). It also explicitly carves out the sibling it is not: 'For totals across users use clockify_summary_report', so an agent can separate it from clockify_detailed_report and clockify_summary_report without opening any schema.

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 a clear routing rule to an alternative ('For totals across users use clockify_summary_report') and enumerates the filter dimensions, which tells the agent when this tool is the right fit. It stops short of a full when-not statement (e.g. when to prefer clockify_detailed_report or clockify_get_time_entry for a single entry), so it is strong but not exhaustive.

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