p4_diff

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It merely says 'Show differences' without explaining whether the operation is read-only, what output format to expect, whether files must be opened in a workspace, or how the tool behaves with unopened or non-existent files.

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?

The description is only one sentence, which is concise, but it lacks the substance needed to be useful. It is under-specification rather than efficient writing; it does not explain the scope or context of the diff operation, making the sentence too sparse to guide an agent effectively.

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 and no annotations, the description is the only source of context. It fails to communicate what output the agent will receive, what options are available (e.g., diff format, recursion), or any prerequisites. For a tool operating on source control files, this level of detail is insufficient for correct invocation.

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?

The schema provides descriptions for both parameters ('files' and 'path'), achieving 100% coverage. However, the description adds no additional semantics beyond what the schema already states, such as clarifying that 'path' is optional and overriding the working directory. It defaults to baseline 3 because schema coverage is high.

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 states a clear verb ('Show') and resource ('differences for files'), but it is vague about the type of differences (e.g., workspace vs. depot, between revisions). It does not distinguish this tool from siblings like p4_status or p4_info, which also deal with file states.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not mention that this tool is preferred over p4_status for viewing content changes, or that p4_raw_command could be used for low-level diff operations. There are no usage conditions or exclusions.

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