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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description is consistent with them. It adds genuine behavioral context beyond the annotations: results are merged and newest-first, the timeline spans six entry kinds, and it is the shared write surface for teammates. The only unaddressed behavior is return shape, which is minor for a read tool.

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 sentences with zero filler: core function is front-loaded in sentence one, usage guidance in sentence two, ecosystem context in sentence three. Every sentence earns its place and nothing important is buried.

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 list tool with four schema-documented parameters and safety annotations, the description covers purpose, ordering, content scope, and selection conditions — a complete picture for invoking it correctly. Minor gaps: it doesn't hint at the return shape (no output schema exists) or explain whether combining multiple `types` values is AND or OR filtering.

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 coverage is 100%, so the baseline is 3. The description adds value by enumerating the entry kinds the `types` filter accepts (progress notes, comments, status changes, handoffs, artifacts, escalations), which goes beyond the schema's generic 'e.g.' example, and it motivates filtering by saying the tool can 'filter to a single kind of entry.'

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 ('Read') and resource ('the merged, newest-first activity timeline for a task'), then enumerates the exact content types: progress notes, comments, status changes, handoffs, artifacts and escalations. This distinguishes it from the sibling get_task, whose limited 30-entry activity window is explicitly called out, and from get_task_review.

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?

Explicitly names the alternative and the switching condition: 'Use this when get_task's `activity` window (30 entries) isn't enough, or to filter to a single kind of entry.' It also identifies the write-side siblings (add_progress_note, add_comment) whose output lands on this surface, giving the agent a sense of the tool's ecosystem role.

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