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

readOnlyHint=true already establishes the safe-read profile, so the description isn't burdened with that. It adds useful return-content context ('final label, agreement, notes and flags') and a pagination cue, but omits whether results exist only for closed tasks, how paging terminates, or any ordering/rate-limit behavior.

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 short sentences with no filler, and the returned-field summary leads before the paging note. It is efficient, though arguably under-specified rather than deliberately concise.

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, 0% parameter coverage, and no annotation detail beyond readOnly, the description leaves too much open: three of four parameters are unexplained and the response shape is only hinted at by a field list. For a 4-parameter retrieval tool this is insufficient.

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% across 4 parameters, so the description must compensate. It explains only starting_after ('the last item id') and implies the paging pattern; limit, since, and taskId receive no clarification of format, units, or effect.

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?

The description names the resource precisely: 'Finished items with final label, agreement, notes and flags,' which tells an agent this returns completed/labeled results rather than task metadata. However, it never differentiates itself from siblings like get_task or list_tasks, and the verb is only implied by the tool name.

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?

There is no guidance on when to call this versus get_task, list_tasks, or the other read siblings, nor any prerequisite (e.g. that the task must be finished/closed). The only usage note is the pagination mechanism, which is a mechanical detail rather than a selection criterion.

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