pbs_tape_drive_delete

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

Discloses mutation nature, risk level (RISK_LOW: config-only), dry-run default, synchronous execution, return value for confirm=True, and lack of undo. With no annotations, description fully carries behavioral burden, covering safety, idempotency, and side effects.

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?

Extremely concise yet informative: uses structured labels (MUTATION, RISK_LOW, Dry-run, No UNDO) and front-loads key information. No unnecessary words; every sentence earns its place.

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 all necessary aspects: deletion action, risk, dry-run vs execute, return format, side effects on jobs, and re-creation alternative. References output schema implications. Complete for a delete tool with given complexity.

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 has 100% description coverage, so baseline is 3. Description adds context for confirm parameter (dry-run vs execution) and mentions requirement of PROXIMO_PBS_* config. Does not add much beyond schema, but the added context is valuable.

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?

Description starts with 'MUTATION: delete a PBS tape drive config', clearly stating the verb (delete) and resource (tape drive config). It distinguishes from sibling tape drive tools (create, update, get, list, etc.) by specifying it's a deletion 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?

Explains dry-run default and confirm=True execution, with implications: 'No UNDO primitive — tape-backup jobs referencing this drive fail until it is re-created with pbs_tape_drive_create'. Provides explicit when-to-use guidance and alternative for re-creation.

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