Get task diff

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description usefully adds the return shape (file list, stat and patch), which matters since there is no output schema, but it says nothing about truncation via max_chars or the state a task must be in.

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 compact sentence that front-loads the resource and then the payload contents. No filler, though it is arguably too terse given the missing usage and truncation context.

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, the description does partially cover the return value (file list, stat, patch). However it omits when the tool is applicable and how max_chars affects output, leaving meaningful gaps for a tool that can return large patches.

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 only 50%: task_id is documented in the schema, but max_chars has no description anywhere. The description does not mention the character cap or what happens when the patch exceeds it, so it fails to compensate for the gap.

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 (get) and resource (the diff of changes a worktree-isolated task made), and enumerates what the diff contains (file list, stat, patch). This distinguishes it from siblings like get_task and get_task_logs, though it doesn't explicitly name them.

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 statement of when to call this versus alternatives, nor any precondition such as the task being finished or isolated to a worktree. The reader must infer usage entirely from the phrase 'worktree-isolated task'.

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