pbs_tape_key_list

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

Without annotations, the description carries the full burden. It clearly states the tool is read-only, lists the specific fields returned, and explicitly mentions that key material or password is never returned. This transparency is high, though it could add details about rate limits or authorization beyond config requirements.

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, efficient sentence that front-loads the most important information (READ-ONLY) and includes all key details without unnecessary words. Every part is informative and 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 that an output schema exists and there is only one optional parameter, the description is fairly complete: it covers purpose, input prerequisites, output metadata, and safety. It could be slightly more complete by mentioning ordering or pagination, but it is adequate for tool selection.

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 only parameter (proximo_target) is fully described in the input schema (100% coverage), and the tool description adds no additional semantic meaning beyond what is already in the schema. The baseline of 3 is appropriate.

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 existing PBS tape encryption keys, specifies it is READ-ONLY, and lists the public metadata fields returned. It distinguishes itself from sibling tools like pbs_tape_key_create by focusing on listing only public metadata.

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 notes the tool is read-only and requires PROXIMO_PBS_* configuration, providing clear context for when to use it. However, it does not explicitly state when not to use it or compare it to similar list tools like pbs_encryption_key_list, so it falls short of a 5.

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