pbs_tape_drive_restore_key

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

With no annotations, description fully covers mutation effect, risk level, secret contract for password, dry-run vs execute behavior, synchronous execution, return format, and config dependency.

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?

Very concise and well-structured with tags like MUTATION, RISK_MEDIUM, SECRET CONTRACT. Every sentence adds value.

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?

Covers key behavioral aspects and return, but could mention prerequisites like drive having media loaded with a key to restore.

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 3. Description adds security note about password not logged but doesn't elaborate on drive or proximo_target beyond schema.

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 restores a tape encryption key from a drive's mounted media, but does not explicitly differentiate from sibling pbs_tape_key_create beyond mentioning it mirrors its rating.

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?

Provides context on confirm flag and config requirements, but lacks explicit guidance on when to use this tool vs alternatives like pbs_tape_key_create or pbs_tape_key_update_password.

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