pbs_datastore_active_operations

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

Discloses read-only nature and acknowledges a schema artifact ('live schema declares returns:null and its description is a copy-paste artifact'), providing transparency about potential inconsistencies. No annotations are present, so the description carries full burden; it handles this 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?

Extremely concise: two sentences. The purpose is front-loaded with 'READ-ONLY', and each sentence provides essential information without redundancy. No wasted words.

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 purpose, usage context (before unmount), prerequisites (config), and a behavioral caveat (schema artifact). Output schema exists, so return details need not be in description. For a simple read-only tool, this is nearly complete; missing only potential format of counters.

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% with both parameters documented. The description adds no new parameter-specific details beyond the schema, but the mention of PROXIMO_PBS_* config indirectly relates to the 'proximo_target' parameter. Baseline 3 is 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 is read-only and returns in-flight operation counts (expected read/write counters) for a datastore. The phrase 'Useful before pbs_datastore_unmount' distinguishes it from sibling tools like pbs_datastore_status, making the tool's specific role evident.

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 advises use before pbs_datastore_unmount and notes the PROXIMO_PBS_* config prerequisite. While it does not list explicit alternatives or when not to use, the guidance is sufficient for an agent to determine appropriate context.

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