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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description contributes only "recent" and "summaries," which weakly imply a date window and reduced detail; it says nothing about pagination behavior (the `cursor` param suggests it exists) or scoping. With annotations carrying the load, this adds minimal incremental context.

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?

It is a single four-word phrase with no padding, so nothing is wasted, but it is under-specified rather than tight — the brevity comes at the cost of the information an agent needs. Front-loading the purpose is fine; there is simply almost nothing behind it.

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?

An output schema exists, so return values need not be explained, but for a 7-parameter, 0%-coverage listing tool with several near-duplicate siblings the description is far too thin. Filtering semantics, pagination, and sibling disambiguation are all absent.

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?

Seven parameters with 0% schema description coverage and no parameter detail in the description. The meaning of `slim`, `status`, `task_types`, `cursor`, and especially `connection_context` (which has a strict regex pattern) is left entirely undocumented, and the description does not compensate for the coverage gap as required at this level.

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?

"List recent task summaries" gives a verb and a resource, but "recent" is undefined (the 7-day default in `days` is the only hint) and "summaries" is ambiguous against siblings like tasks_latest, tasks_get_status, and tasks_list_create_history. An agent cannot tell from the text which of those four list/read task tools to pick.

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?

The description gives no when-to-use guidance, no prerequisites, and never names an alternative such as tasks_latest or tasks_get_status. The sibling set contains at least four overlapping task-reading tools, so the absence of routing guidance is a real gap.

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