pbs_datastore_unmount

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

With no annotations, description fully discloses mutation behavior: datastore becomes unavailable, in-flight operations aborted, jobs fail until re-mounted, async operation (UPID), null return for ok, and config requirement (PROXIMO_PBS_*).

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?

Description is concise yet comprehensive, front-loaded with MUTATION label and risk level. Uses clear structure: risk, consequences, usage steps. 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?

For a tool with 3 parameters and output schema, description explains return values (null/UPID), dry-run behavior, and impact on operations. Covers all necessary context 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 coverage is 100%, baseline 3. Description adds value by explaining 'confirm' as dry-run toggle and 'proximo_target' as multi-target selection, reinforcing meaning 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 the tool's purpose: unmount a removable device backing a datastore, using specific verb 'unmount' and resource 'datastore'. It distinguishes from sibling tools like pbs_datastore_mount (reverse) and pbs_datastore_active_operations (pre-check).

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 guidance: check pbs_datastore_active_operations first, dry-run by default, confirm=True to execute, and reverse with pbs_datastore_mount. Does not explicitly list when not to use, but context is clear.

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