p4_unshelve

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

There are no annotations provided, so the description must carry the full behavioral disclosure burden. It only states the action without revealing side effects, such as whether unshelving overwrites workspace files, whether force is required for open files, or what happens if the changelist is already integrated. This is a meaningful 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 short sentence with zero filler words. It front-loads the core verb and object, making the purpose instantly scannable. No space is wasted on redundant restatement of the 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?

Given the absence of annotations and an output schema, the description is too sparse to be fully actionable. It does not explain return values, failure modes, force behavior, or the effect of the optional files parameter. The schema covers parameter syntax, but the behavior around a Perforce unshelve operation is left undocumented.

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 has 100% parameter description coverage, so the schema already documents changelist, files, force, and workspacePath. The description adds no parameter-level meaning, but the baseline of 3 applies because the schema carries the heavy lifting.

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 ('Unshelve') and resource ('files from a shelved changelist'), making the operation immediately identifiable. It clearly distinguishes itself from the sibling p4_shelve and other p4 operations without requiring the agent to inspect the schema.

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?

The description implies its use case: restoring files from a shelf. However, it does not explicitly state when to choose this over alternatives like p4_shelve, nor does it mention prerequisites such as needing an existing client workspace or a connection to Perforce. The usage context is understandable but left mostly to inference.

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