pbs_datastores_list

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

With no annotations, the description carries the full burden. It explicitly states 'read-only', which implies no destructive side effects. It describes the return structure but lacks details on error conditions, pagination, or authorization beyond the config requirement. Still, the core behavioral trait is 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?

The description is four sentences with no fluff. It front-loads the core purpose ('List all PBS datastores (read-only)'), then provides return info, alternatives, and a prerequisite. Every sentence earns its place.

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 presence of an output schema (context indicates 'Has output schema: true'), the description does not need to detail return values, but it usefully highlights key fields. It covers the parameter adequately and offers alternative guidance. Missing error handling or edge cases, but acceptable for a simple list 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 input schema has 100% coverage for the single parameter 'proximo_target', and the description does not add any additional meaning beyond what the schema already provides. The baseline of 3 applies as the description does not enhance 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 tool lists all PBS datastores as read-only and specifies the return fields (store name, backend type, mount status). It distinguishes itself from siblings pbs_datastore_status and pbs_datastore_get, making the purpose unambiguous.

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 explicitly tells when to use alternatives: 'Use pbs_datastore_status for runtime usage statistics or pbs_datastore_get for full configuration.' It also notes a prerequisite: 'Needs PROXIMO_PBS_* config.' This provides clear context for selection.

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