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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so "Read-only" is redundant. The description does add value beyond them: newest-first ordering and the fact that a null ended_at means the entry is still running — a genuinely useful behavioral detail.

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 front-loaded sentences, dense with useful detail, including a compact enumeration of returned fields. Minor waste in repeating the read-only fact already carried by annotations, but nothing is buried or padded.

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, and the description partly compensates by naming the returned fields and the null-duration semantics. However, the 'limit' parameter and default page size are left entirely undocumented, which matters for a list tool an agent may need to page through.

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 0%, so the description must carry the load, and it explains two of three parameters well: 'days' as a rolling window over started_at and 'task_id' as a single personal task. The 'limit' parameter (max 100) is never mentioned, and the integer-or-string union on task_id is unexplained.

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 caller's time entries"), plus the scope (caller's own, active workspace) and ordering (newest work first). That is enough to separate it from a write-side sibling like log_time 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 clear operating context: no required filters, optional rolling 'days' window and optional single 'task_id'. It does not name an alternative tool or state when to prefer another listing, so it stops short of full routing guidance.

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