pbs_tape_pool_get

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 states READ-ONLY, indicating no modification, but does not disclose other behavioral aspects such as error handling, permissions required, or whether the operation is safe. Given the lack of annotations, the description provides basic but insufficient behavioral disclosure.

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 sentence that conveys essential information: read-only nature, target resource, and prerequisite config. It is concise and avoids fluff, though it could benefit from slight restructuring to improve scannability.

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?

The presence of an output schema reduces the need to describe return values. However, the description does not explain what 'config' includes or any guarantees about the response. Given the tool's simplicity and the output schema, the description is adequate but could be more complete.

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%, with both 'name' and 'proximo_target' already well-described in the input schema. The description adds no extra semantic meaning beyond 'get one PBS tape media pool's config', so the baseline of 3 applies.

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?

Description clearly states it gets one PBS tape media pool's config, with the READ-ONLY prefix emphasizing it's a retrieval operation. The verb 'get' and resource 'PBS tape media pool config' directly indicate its function, distinguishing it from sibling tools like create/delete/update/list.

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 mentions 'Needs PROXIMO_PBS_* config' as a prerequisite, providing some guidance. However, it does not explicitly state when to use this tool over alternatives like pbs_tape_pool_list, nor does it specify scenarios where this tool is preferred. The guidance is minimal.

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