read_task_resource

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

No annotations are provided, so the description carries the full behavioral burden. It discloses only one trait, paging to conserve context, and says nothing about read-only safety, whether content is truncated or lossy, what happens at the end of a payload, or what error conditions exist for an invalid resource or task_id.

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?

A single tight sentence with no filler, and the rationale (protecting the context window) is front-loaded alongside the action. It is under-specified rather than verbose, so the only cost is that nothing follows the one sentence.

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 4-parameter paginated read tool with zero annotation and zero schema-description coverage, the definition leaves too much implicit: it never mentions task_id, does not explain how limit and offset interact, and gives no hint of how this relates to the sibling tools that produce or inspect tasks. The existing output schema offsets the need to describe return values, but not the missing call semantics.

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% and the 'resource' parameter has no enum, so the description's enumeration of diff/transcript/assignments is genuinely the only documentation of valid values. Beyond that, task_id, limit, and offset are left untouched, with only the phrase 'Page through' hinting at offset/limit semantics and no indication of what units limit uses.

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 gives a specific verb ('Page through') and enumerates the payload types it reads (diff/transcript/assignments), which maps onto the 'resource' parameter. It is clear enough to distinguish the operation from sibling task tools like get_task_status or dispatch_task, though 'payload' is vague about where the content comes from.

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 clause 'to protect the controller context window' implicitly states the condition for use: call this when a payload is too large to read at once. However, no alternative is named (e.g., when to use this instead of preview/status tools), and there is no guidance on when a full read is acceptable or on typical paging strategy.

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