pbs_datastore_mount

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

No annotations provided, so description carries full burden. It covers mutation, dry-run default, execution with confirm=True, asynchronous nature (UPID), tracking via pbs_tasks_list, and reverse operation. Lacks explicit destructive hint but 'availability transition' implies state change; overall transparent.

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 efficient though multi-sentence. Starts with clear type and action, then explains behavior, return, tracking, and reverse. Each sentence adds information; not overly verbose but could be slightly more structured.

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 no annotations and moderate complexity (3 params, async, output schema exists), description covers mutation, default behavior, execution, async nature, return values, tracking, reverse, and config dependency. Adequately complete for an informed decision.

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% (all 3 params described). Description adds value by explaining confirm's dry-run semantics and proximo_target's config requirement, beyond what the schema states.

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 clearly states verb 'mount' and resource 'removable datastore', labels it as 'MUTATION', and explicitly names the reverse sibling 'pbs_datastore_unmount', distinguishing it from other sibling tools.

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?

Explicitly describes dry-run behavior, confirmation requirement, and the reverse operation. Mentions config requirement (PROXIMO_PBS_*). Does not explicitly list when not to use, but sibling differentiation and fail-safety of dry-run provide adequate guidance.

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