pbs_tape_drive_unload

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

No annotations provided, so description carries full burden. Discloses mutation, risk level, robotic action, dry-run default, confirm execution, response format, lack of undo, and config requirement. All critical behavioral traits covered.

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?

Every sentence adds value: purpose, risk, default behavior, execution, undo, config. No redundancy, well-structured and front-loaded.

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 4 parameters, output schema present, and complexity of robotic tape action, description covers overall behavior, risk, and worklow. Lacks details on error states or drive empty handling, but output schema mitigates need for return format description.

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 baseline is 3. Description adds context about confirm=true executing and returning UPID, but does not significantly enhance parameter understanding beyond schema descriptions for target_slot or proximo_target.

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?

Clearly states it returns a drive's mounted media to a changer slot. Distinguishes from siblings by explicitly mentioning the reverse operation pbs_tape_drive_load_slot, and context shows many tape drive 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?

Explains when to use (unload media), dry-run vs execute behavior, and mentions no undo primitive with reverse tool named. Does not explicitly state when not to use but provides sufficient context.

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