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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered at no cost to the description. The description's only added behavioral signal is that related entities (client, project, invoice) are included in results, which is mild context. It does not cover pagination behavior or result size, which with 8 filter params would have been useful.

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 with no padding; the resource and returned fields come first and the underlying endpoint is appended as a trailing reference. Nothing is wasted, though the second sentence is a raw API path that adds little for an agent.

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 carries the burden of signaling return content, and it does so by enumerating the key fields and linked entities. Combined with a fully documented schema, an agent has enough to call and interpret the tool; only pagination/result-volume behavior is left unstated.

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% with all 8 optional parameters documented in-schema (page, sort, filter, number, status, per_page, client_id, client_status). The description adds no parameter-level detail — not even which filters are the common ones — 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 ('List') and resource ('tasks / time entries') and goes further by naming the relationships returned (time_log, duration, rate, client, project, invoice). An agent can tell it apart from the other list_* siblings by resource. It stops short of explicitly contrasting itself with sibling list tools, so it lands just below the top tier.

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 only implied by the name and the returned-field list; there is no statement of when to prefer this over list_projects or list_expenses, no mention of pagination expectations, and no prerequisites or exclusions. Adequate for an obviously-scoped list endpoint, but nothing routes the agent.

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