pdm_pbs_datastores_list

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

Declares READ-ONLY and no state change, and notes it's proxied through PDM with live-verified data (PDM 1.1 -> PBS 4.2). Auth requirements stated via 'Needs PROXIMO_PDM_* config.' No annotations to contradict.

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?

Very concise: three short sentences. Front-loaded with purpose, then usage context. No extraneous information.

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 tool's simplicity, output schema exists, and schema covers all parameters, the description is complete. It explains scope, behavior, alternatives, and auth requirements without omission.

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 is 3. Description adds context by stating remote is a 'PDM-registered PBS remote name, from pdm_remotes_list,' which helps the agent understand the parameter's origin. This adds value beyond the 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?

Description clearly states 'list datastores on a PDM-registered PBS remote' with a specific verb and resource. It distinguishes from sibling tools pbs_datastores_list and pdm_pbs_snapshots_list.

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 states READ-ONLY, no state change, and provides when-to-use alternatives: 'For snapshots within a datastore use pdm_pbs_snapshots_list; to query PBS directly without PDM, use pbs_datastores_list.' Also mentions required config PROXIMO_PDM_*.

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