p4_integrated

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

No annotations are present, so the description carries the full behavioral disclosure burden. 'Show' implies a read-only operation, but it does not mention whether a workspace is required, how filespecs are expanded, or what the output format looks like.

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 states the action and the key scoping concept with no filler. It is appropriately sized for a straightforward read-only history tool.

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?

The tool is simple and the parameters are well documented, but there are no annotations and no output schema. The description does not cover return format, prerequisites, filespec syntax, or behavior differences from related Perforce tools, leaving moderate gaps for an agent to resolve elsewhere.

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 100%, so the schema already documents all four parameters and the baseline of 3 applies. The description's reference to 'source/target paths' loosely maps to sourcePath and targetPath, but it adds no additional meaning beyond the schema.

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 the verb 'Show' and the resource 'integration history', scoped to source/target paths, which is clear and specific. It does not explicitly differentiate itself from siblings like p4_integrate or p4_interchanges, but the core action is unambiguous.

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 use this tool versus alternatives such as p4_integrate, p4_interchanges, p4_merge, or p4_filelog. The description only states what the tool does, leaving usage context entirely to inference.

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