pdm_pbs_datastores_list

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

No annotations provided, so description carries full burden. It discloses the output shape ('Live-verified shape') and config dependency, but does not mention side effects, rate limits, or error scenarios. The 'DIAGNOSE (LOW)' label hints at non-destructive operation but is not explicit.

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?

The description is extremely concise—four short lines—and front-loaded with the verb and resource. Every sentence serves a purpose: purpose, parameter guidance, output shape, and config requirement. 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?

Given the existence of an output schema (not shown but indicated), the description provides the key output shape and config prerequisites. It could be improved by mentioning possible errors or pagination, but for a list operation, it is nearly 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?

The description adds meaning to the 'remote' parameter by linking it to 'pdm_remotes_list', compensating for the schema's lack of description for that parameter. The 'proximo_target' parameter is already well-described in the schema. Overall, the description enhances parameter understanding.

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 verb 'list' and the resource 'datastores on a PDM-registered PBS remote'. It includes a severity label 'DIAGNOSE (LOW)' and distinguishes from sibling 'pbs_datastores_list' by specifying PDM registration.

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?

The description tells the agent that 'remote' should come from 'pdm_remotes_list' and that the tool needs 'PROXIMO_PDM_* config'. However, it does not explicitly state when to use this tool versus alternatives like 'pbs_datastores_list', nor does it provide exclusions.

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