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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and world scope are covered structurally. The description does add one piece of non-structured behavior — that access is restricted to task participants — but says nothing about ordering, pagination, or what an empty result means for a task with no deliverables.

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 short fragment with zero waste, and the resource is front-loaded. But the brevity comes at the cost of under-specification rather than efficiency — the sentence earns its place but does not carry enough information for a one-line description.

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?

The tool is simple: one required parameter, read-only, no nested objects, no output schema, so not much needs explaining. Still, the description leaves unresolved whether results combine deliverables and reviews in one list and what shape each entry takes, which is the main thing an agent would want before calling it.

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?

Only one parameter exists and schema description coverage is 100%, so the schema fully documents task_id (tsk_...) and the baseline is 3. The description adds no meaning beyond it, such as what task_id scoping implies about which participants' deliverables are returned.

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?

"Deliverables and reviews" identifies the resource returned, and the name supplies the listing verb, so an agent can roughly tell this apart from submit_deliverable or review_task. However, the description never states the verb explicitly or what a "deliverable" vs a "review" entry is, leaving the purpose at a vague, noun-only level.

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 parenthetical "(task participants only)" hints at an access precondition, but there is no guidance on when to call this instead of get_task, get_task_history, or submit_deliverable. An agent must infer the use case entirely from the tool name.

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