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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description goes well beyond them: it discloses that the result set is permission-dependent (all entries for Administrator/ProjectManager, only the caller's own for a Member) and that a Free workspace returns a plan-limit message. Permission-scoped output and plan-gated failure behavior are exactly the non-obvious traits an agent needs before calling.

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 resource and the returned values, then the plan constraint. Every clause carries information — the em-dash enumeration of what is returned and the role split both earn their space; there is no filler.

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 no output schema, the description carries the burden of describing return values and it does so (total minutes, effort-derived estimate, entries). It omits finer detail such as whether the estimate is null when effort is unset or whether entries are truncated for large tasks, which keeps it from a 5 for a non-trivial aggregate.

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?

There is a single required parameter with 100% schema description coverage, so the schema already documents taskId fully. The description adds no format, scope, or edge-case detail about taskId beyond what is in the schema, making 3 the appropriate baseline.

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 ('Time logged on one task') and enumerates the three things returned: total minutes, the estimate from effort, and the entries. An agent can tell this is a per-task time aggregate rather than the raw entry listing of list_time_entries. It does not name any sibling explicitly, so it stops short of a 5.

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 hard prerequisite — 'Pro plan only (a Free workspace gets a plan-limit message)' — which is real usage guidance. However, it never says when to reach for this versus get_task, list_time_entries, or get_earned_value, so the choice among alternatives is left to inference.

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