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

The readOnlyHint annotation already signals this is a safe read operation. The description adds 'Paginated' and the REST endpoint reference, which provides useful behavioral context without contradicting any annotations. A higher score would require disclosure of rate limits or auth specifics, but these are not critical for a simple list operation.

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 the core purpose, then listing filters compactly. Every word earns its place; no redundant or verbose content.

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 list tool with full schema coverage and readOnlyHint, the description covers the core purpose, all filter dimensions, and pagination. Although no output schema exists, the return value is inherently 'a list of time entries' and the REST endpoint is given. It could mention the response shape, but it's not essential for this resource type.

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 11 parameters are already documented. The description summarizes the filter dimensions (user, project, client, task, date range, running/billed, updated_since) but does not add new meaning beyond what the schema provides. It also omits pagination parameters (page, per_page) in the summary, though they are in schema.

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 clearly states 'List time entries' with a specific verb and resource, and the optional filters are enumerated. It distinguishes from sibling tools like harvest_get_time_entry (single entry), harvest_create_time_entry, and other resource-specific list tools.

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?

Usage is implied for listing multiple time entries with optional filters, but no explicit when-to-use or exclusion guidance is provided. The description doesn't mention alternatives for single-entry retrieval, though the name and resource make it fairly obvious.

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