pbs_tape_drive_rewind

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

With no annotations provided, the description fully carries the burden. It explicitly states it is a mutation, low risk, repositions only the tape head, no mount/unmount, no data touched, and mentions the dry-run/execute pattern. It also notes configuration requirements (PROXIMO_PBS_*). This is comprehensive for a simple rewind 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 concise (5 sentences) and front-loaded with key information: MUTATION label, behavior, risk level, dry-run default, and config needs. Every sentence adds value; there is no fluff.

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 three parameters (100% schema coverage) and an output schema, the description covers behavior, risk, dry-run pattern, and configuration. It does not mention prerequisites like the drive must have a tape loaded, but this is reasonable for a rewind operation. Overall, it is nearly complete.

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 description coverage is 100%, so baseline is 3. The description adds minimal extra meaning—it reiterates the confirm parameter's effect, but the schema already describes all parameters clearly. No additional semantics are provided beyond what the schema offers.

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 states it rewinds a drive's mounted tape to its beginning. It labels itself as MUTATION and RISK_LOW, and the verb 'rewind' with the resource 'drive's mounted tape' is specific and distinct from siblings like pbs_tape_drive_load_media or pbs_tape_drive_unload.

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 (returns a PLAN) and how to execute with confirm=True, providing clear usage context. However, it does not explicitly contrast this tool with alternatives (e.g., when to rewind vs. load/unload), missing full exclusion guidance.

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