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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, closed-world), but the description adds genuinely non-obvious behavior the annotations cannot convey: default sort order (newest first), permission-dependent result shape (owner sees all entries with hourly rates in cents; other members see only their own without rates), and an aggregate total-minutes value computed over the filtered set. That is substantial extra context for a read tool.

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 tight sentences with no filler. The core purpose and ordering are front-loaded, then access semantics, then the aggregate return, each sentence carrying distinct information.

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?

There is no output schema, so the description must carry return-value information, and it does: it names the fields returned, the sort order, the rate visibility rule, and the extra total-minutes aggregate. Combined with full-schema parameter coverage and read-only annotations, an agent has everything needed to call and interpret this tool.

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 each of the six parameters (from, to, limit, cardId, userId, boardId) is already documented with format and constraints. The description only alludes to filtering generically ('everything the filters match') without adding syntax, defaults, or edge cases beyond the schema, so the baseline of 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?

The description states a specific verb ('Lists') and resource ('time entries of a project') and even enumerates the returned fields (who logged each, the task, the day, the minutes, billable flag), which is far more than a tautology. It does not, however, name or distinguish itself from nearby siblings like get_time_report, get_week_timesheet, get_task_time, or list_unbilled_work, so the agent must infer the boundary.

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 rather than prescribed: the agent can infer this is the per-project time-entry listing, and the role-dependent behavior tells it what a given caller will see. But there is no explicit when-to-use-this-vs-alternatives guidance against the several other time-reporting tools in the sibling list, and no stated prerequisites beyond an implicit projectId.

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