pbs_tape_changer_delete

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

With no annotations, description fully handles transparency: mutation type, risk level, dry-run behavior, synchronous execution, return format, side effects (drive failure), and config requirements. No gaps.

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?

Front-loaded with key info (MUTATION, RISK_LOW). Every sentence is meaningful and concise. No filler.

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 output schema exists, description covers return values, side effects, and prerequisites. Complete for a deletion tool with dry-run capability.

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 description adds little beyond (e.g., the config requirement for proximo_target). It doesn't explain name or confirm beyond what schema provides. Baseline 3 is appropriate.

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 deletes a PBS tape changer config, with a specific verb and resource. It distinguishes from siblings like pbs_tape_changer_create by mentioning recreation, and from other tape changer tools by being the delete operation.

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 explicit context: dry-run by default, confirm=True to execute. Warns about no UNDO and impact on drives. Could be clearer on when to use vs. not use this tool, but it implies usage for deleting changers.

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