pbs_tape_drive_inventory_update

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

With no annotations, description carries full burden. Discloses mutation, physical operation, duration scaling, dry-run behavior, return formats (PLAN or status+UPID), and config requirement. Covers key behavioral aspects well.

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?

Efficient and front-loaded: begins with 'MUTATION:', then action, risk, modes, return, config. Every sentence adds value. 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?

Covers core operation, risk, dry-run, return values, and config. Lacks error handling or prerequisites, but given complexity and output schema presence, it's fairly 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 coverage is 100%, so parameters are well-described there. Description adds context for 'confirm' (dry-run vs execute) and 'read_all_labels' (re-read even inventoried), but largely restates schema info. Baseline 3 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?

Clearly states it's a mutation that queries the changer and loads+reads unknown cartridges, storing results to the media database. Specifies dry-run vs execution modes. Lacks explicit differentiation from sibling tool 'pbs_tape_drive_inventory', which might be read-only.

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?

Warns about physical cycling and time scaling with library size. Recommends dry-run default, explains confirm=True for execution. Notes configuration requirement (PROXIMO_PBS_*). Does not mention when to avoid or alternative tools.

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