pbs_list_datastores

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so no extra safety context is needed. The description adds detail about the output content (path, scheduled jobs) but does not disclose other behavioral traits such as potential for large responses or pagination. It does not contradict annotations.

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?

A single, front-loaded sentence with no wasted words. It states the action, the resource, and the two key details (path, scheduled jobs) in under 20 words, making it immediately scannable.

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 is a simple read-only list with no parameters and an output schema, the description is adequate. It does not explain the return structure (but the output schema covers that) or edge cases (e.g., no datastores configured), which are minor gaps for such a straightforward tool.

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 schema defines no actual parameters (empty ListDatastoresInput object). With zero parameters, the baseline is 4, and the description correctly adds no parameter explanations. The required 'params' wrapper is a structural artifact but not a semantic parameter.

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 uses a specific verb-resource pair ('List every configured PBS datastore') and adds the precise scope ('every', 'with its path and any scheduled GC/prune jobs'). This clearly distinguishes it from siblings like pbs_datastore_status or pbs_list_snapshots.

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 implies when to use this tool: whenever you need an overview of all configured datastores, including paths and scheduled GC/prune jobs. It does not mention alternatives or exclusions, but the context is clear enough for an AI agent to select it appropriately among the sibling tools.

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