pbs_tape_pool_list

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

Declares READ-ONLY behavior, which is useful since no annotations are provided. However, does not disclose further traits like authentication needs beyond config, or any potential locking implications.

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?

Two short, front-loaded sentences. No unnecessary words. Efficient and 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 presence of an output schema and simple purpose, the description covers the basics: it lists configured pools, requires specific config, and is read-only. Minor gap: no explanation of what 'configured' means, but acceptable.

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 the schema already fully describes the optional parameter. The description does not add additional meaning or context for the proximo_target 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?

Clear verb 'list' and resource 'configured PBS tape media pools'. Distinguishes from sibling tools like create/get/delete/update by explicitly stating it lists configured pools and being labeled READ-ONLY.

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?

Mentions prerequisite config (PROXIMO_PBS_* config) and that it is READ-ONLY, but does not explicitly guide when to use this vs other tape pool tools like pbs_tape_pool_get for a specific pool.

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