pbs_tape_backup_job_run

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

No annotations provided, but description fully discloses mutation nature, risk level, side effect (drive busy), dry-run safety, and the unusual return format (null, never 'submitted').

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?

4 concise sentences with clear labeling (MUTATION, RISK_MEDIUM, SCHEMA QUIRK). Every sentence adds value; no redundancy.

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 mutation behavior, return type, dry-run safety, config requirement, and contrasts with sibling. Output schema exists but description already explains return value. Complete for a moderate-complexity tool.

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 value by explaining confirm's effect (dry-run vs execute) and clarifying proximo_target's optional selection of multi-target config. Not significantly beyond schema but helpful.

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 'manually run a preconfigured tape backup job, right now.' Explicitly distinguishes from sibling pbs_tape_backup by contrasting return types (null vs UPID).

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 usage: dry-run default (returns PLAN), confirm=True executes. Notes risk (drive busy), necessary config (PROXIMO_PBS_*), and contrasts with sibling. No exclusions needed.

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