Read one task with its subtasks

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

No annotations are provided, so the description carries the full burden. It discloses the full behavioral scope: the complete task content, subtasks, answers, replies, declines, uploads with inputId, and reply files with id. It also reveals the group-behavior nuance (grptsk_ groupId) and the fact that files are intended for download_attachment. It does not discuss errors, permissions, or side effects, but the read-only nature is clear from 'Read' and 'get'.

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 no filler. The opening sentence states the purpose, the second enumerates the returned content compactly, and the third gives follow-up guidance. The most decision-relevant information is front-loaded.

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 tool with only one required parameter and no output schema, the description covers prerequisites, return content, file-id semantics, and a group-copy follow-up. It does not specify the exact response structure, but the enumerated content types give an agent enough to invoke the tool and interpret the result.

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% and the schema already documents task_id as 'The tsk_ id.' The description adds meaningful provenance guidance: the task_id comes from query_tasks or get_activity, and the grptsk_ groupId context clarifies multi-recipient tasks. This goes beyond the bare schema, so a slightly-above-baseline score is warranted.

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 clearly identifies the resource: one task plus every appended subtask. It states a specific verb ('Answers') and scope ('what exactly was asked and answered'), and enumerates the content categories (questions, answers, replies, declines, uploads, reply files), which distinguishes it from listing tools like query_tasks and narrower tools like get_task_answer.

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 explicit context: use after query_tasks or get_activity has identified the task. It also routes the agent to get_group_status when the task has a grptsk_ groupId, naming a concrete follow-up alternative. It does not explicitly say when not to use this tool in favor of get_task_answer, so it stops short of perfect exclusion guidance.

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