get_task_diff

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

No annotations are provided, so the description carries the full disclosure burden. It implies read-only behavior via 'Read' and reveals two real traits — the payload is a binary patch and results are paged — but says nothing about truncation signaling, behavior when the task has no diff or is not finished, or permissions.

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 the resource and scoping front-loaded and no filler. It is efficient rather than bloated; brevity is the only concern, not waste.

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 annotations, no output schema, and zero parameter documentation, the description should explain the binary patch format a caller will receive and how to page through it. Those gaps leave an agent guessing about the most consequential aspects of the call.

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%, so all three parameters (limit, cursor, task_id) are undocumented in both schema and description. 'Bounded page' only weakly gestures at limit/cursor, leaving the unit of limit (bytes vs. lines, default 60000), cursor continuation semantics, and task_id meaning unexplained.

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 (an isolated task's Git binary patch) with scope qualifier (bounded page). An agent can tell this returns a raw patch rather than a structured change list, implicitly distinguishing it from get_task_changes. It stops short of naming the sibling it is not.

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 instead of get_task_changes or get_result, and no prerequisites (e.g. must the task be completed?). The phrase 'isolated task' hints at context but never tells the agent which situation selects this tool.

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