pbs_tape_changer_transfer

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

With no annotations, the description fully discloses behavior: it's a mutation, low risk, reversible, no drive interaction, no job interruption. It details dry-run vs execution, synchronous nature, and return format. This is comprehensive and adds value beyond structured fields.

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 exceptionally concise: three sentences cover purpose, risk, and execution details. It is front-loaded with the action and resource, then risk, then dry-run/confirm behavior. Every sentence adds value without redundancy.

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 full schema coverage, presence of output schema, and the description's thorough coverage of behavior, risk, prerequisites, and usage pattern, the tool is completely described for an agent to select and invoke correctly.

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 coverage is 100%, so the schema already describes parameters. The description adds useful behavioral context for the confirm parameter (dry-run vs execute) and explains the overall flow. Some parameter details (like slot numbers) are not enhanced, but the description still provides meaningful addition.

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 explicitly states 'move media from one changer slot to another', which is a specific verb and resource. It distinguishes from sibling tools like pbs_tape_media_move (cross-changer) and other changer operations by emphasizing it's internal slot rearrangement.

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 explains the dry-run default behavior and how to execute with confirm=True, providing clear usage guidance. However, it does not explicitly exclude use cases for alternative tools like pbs_tape_media_move, though the context implies it's for intra-changer moves.

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