pbs_tape_changer_list

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

No annotations are provided, so the description carries the full burden. It discloses the tool is read-only (safe) and the required config, but lacks details on authentication, rate limits, or side effects. The mention of 'config digest' adds some context but is not fully explained.

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 a single, focused sentence that front-loads the purpose and safety indicator ('READ-ONLY'), followed by the specific action and requirement. There is no extraneous information; every word 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 tool is a simple list operation, schema coverage is 100%, and an output schema exists, the description is adequate. It covers the key aspects: what it lists, that it's read-only, and the config requirement. It does not need to explain return values as output schema handles that. Minor omission: no mention of pagination or result limits, but acceptable for a 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?

Schema coverage is 100% for the single optional parameter 'proximo_target', which already has a clear description. The tool description adds that the tool 'Needs PROXIMO_PBS_* config', but this is redundant with the schema description of the parameter. Thus the description adds minimal 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?

The description clearly states the verb 'list' and the resource 'configured PBS SCSI tape changers', and specifies that it includes a config digest. It distinguishes from sibling tools like pbs_tape_changer_create, pbs_tape_changer_get, and pbs_tape_changer_status by focusing on listing all changers.

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 indicates it is read-only and requires PROXIMO_PBS_* config, but it does not explicitly state when to use this tool versus alternatives like pbs_tape_changer_get for specific changers or pbs_tape_scan_changers for scanning. The guidance is implicit rather than explicit.

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