p4_move

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

With no annotations, the description carries the entire behavioral disclosure burden. 'Move/rename files' only implies a mutating operation and provides no details about source deletion, pending changelists, workspace requirements, permission needs, or reversibility.

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 extremely short, consisting of a bare phrase rather than meaningful guidance. Conciseness is beneficial, but here it veers into under-specification for a tool with multiple parameters and no output schema.

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 description is not complete enough for an agent to confidently invoke the tool. It lacks usage context, behavioral caveats, and enough detail to differentiate p4_move from several closely related file-operation siblings.

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 covers all four parameters with descriptions, so the baseline is met. The tool description adds no extra meaning beyond what the schema already provides for source, destination, changelist, and workspacePath.

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 identifies the operation as move/rename on files, which is a specific verb and resource. It distinguishes the action from copy/integrate by using 'move/rename,' though it does not explicitly contrast with sibling tools.

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 about when to use p4_move versus alternatives like p4_copy, p4_integrate, or p4_merge. An agent is left to infer the intended use case from the operation name alone.

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