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

Annotations already declare it a safe read (readOnlyHint=true, destructiveHint=false), so the bar is lower. The description still adds real value beyond them: the concrete return fields, the 80% warning / over threshold logic, and the permission-scoped visibility of time entries. It does not cover pagination or entry-count limits.

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 tight sentences, no filler, with the returned-field list front-loaded. The visibility caveat at the end is the least prominent placement for a constraint an agent must respect, but nothing is wasted.

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 read-only tool with no output schema, the description covers the shape of the response, the pace threshold semantics, and the access-scoping rule. Only the unexplained cardId parameter and absent pagination/limit details keep it from being fully complete.

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% for the single required parameter cardId, and the description never explains it or states that the tool operates on a task id. With only one parameter the gap is small, but the description does not compensate for the missing schema documentation as it should at 0% coverage.

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 ('Reads') and resource ('the time of one task') and then enumerates exactly what is returned: estimate, tracked time, pace status, billable flag, and time entries. This clearly separates it from get_task (task fields) and get_time_report (aggregate reporting), though it never names a sibling explicitly.

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?

No when-to-use guidance against get_task, list_time_entries, or get_time_report. The only usage context is a visibility rule ('project owner reads everyone's entries; any other member only their own'), which informs behavior but not tool selection. Usage is only implied by the single-task scope.

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