phabricator_diff_raw

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

No annotations provided, so description must disclose behavior. It states 'raw diff/patch content' but does not specify the format, size limits, or whether it is read-only. Basic functionality is clear but lacks important behavioral details.

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?

Two concise sentences with no redundant information. Front-loaded with the main action and necessary 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?

No output schema, so description should hint at return value. It mentions 'raw diff/patch content' but does not clarify format (e.g., string, JSON). For a simple tool, it is mostly complete but could be improved with output format details.

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 (diffID) with 100% schema description coverage. The description adds no additional meaning beyond the schema, which already explains the parameter's purpose and how to find it.

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 states the tool's function: getting raw diff/patch content for a Differential diff by diff ID. It also distinguishes itself by referencing phabricator_diff_search for finding the diff ID.

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?

Explicit guidance provided: 'Use phabricator_diff_search to find the diff ID from a revision PHID first.' This clearly tells the agent when to use this tool and what prerequisite step is needed.

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