p4_add

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

No annotations are provided, so the description alone must disclose behavior. 'Add files to Perforce' only communicates a mutating action; it does't mention that files are opened in a changelist, that they must be submitted to take effect, or any dependency on the current workspace. Slightly more concrete than a pure tautology, but far from transparent.

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 a single, front-loaded sentence with zero filler words. It earns its place as a concise action statement, though the brevity undersells the important context around file states and changelists.

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?

Given this is a mutating tool with no annotations and no output schema, the description is incomplete. It omits the crucial 'new files only' semantics, the default changelist behavior, and does not route the agent to alternative tools when files already exist in the depot. The schema handles parameters but not operational context.

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 input schema already describes all three parameters with 100% coverage, including clear explanations for files, changelist, and workspacePath. The description adds no parameter-level meaning, so the baseline score of 3 applies.

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?

Identifies a clear verb and resource: adding files to Perforce. However, it doesn't clarify that 'add' means opening new/untracked files for submission, nor does it distinguish this from sibling tools like p4_edit or p4_copy. The core Perforce meaning of 'add' is left implicit.

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 vs alternatives. The sibling list contains p4_edit, p4_revert, p4_move, and p4_opy, but the descripion never says 'use p4_add for new files, p4_edit for existing files.' The usage context is entirely absent.

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