p4_add

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Add files to Perforce' without mentioning side effects (e.g., opening files in a changelist, requiring a workspace, permission requirements) or reversibility. This is a significant gap for a mutating operation.

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, direct sentence with no wasted words. It front-loads the core action ('Add files to Perforce') and is appropriately sized for a simple tool, though it sacrifices detail for brevity.

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?

Despite having only two parameters and no output schema, the description is too sparse to be complete. It lacks any context about return values, prerequisites (e.g., a valid client workspace), side effects, or how this differs from sibling tools like p4_edit. The absence of annotations compounds this incompleteness.

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?

Both parameters are documented in the input schema (100% coverage), so the schema carries the parameter semantics. The description adds no additional meaning beyond the schema, so it earns the baseline score. The schema already explains 'path' as optional working directory and 'files' as supporting wildcards.

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 uses a specific verb ('Add') and resource ('files' to 'Perforce'), clearly distinguishing it from sibling tools like p4_edit or p4_delete. However, it doesn't explicitly mention that 'add' is for new files or that it opens files for add in Perforce, leaving some ambiguity about the exact operation.

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. It doesn't mention that 'add' is for new files not yet in the depot, nor does it differentiate from p4_edit for existing files. The agent must infer usage from the tool name alone.

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