pbs_tape_drive_get

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

The description explicitly marks the tool as 'READ-ONLY', which is the key behavioral trait. With no annotations, this is valuable. It also mentions the required config, adding operational context. No side effects or additional traits are disclosed, but for a read-only get, this is sufficient.

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 sentences, front-loaded with purpose and read-only status, then prerequisite. Every word earns its place. No fluff.

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 description covers the core purpose, read-only nature, and a prerequisite. With an output schema present, the lack of return value details is acceptable. It could mention that it returns the drive's configuration, but it's implied. Adequate for a simple get 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%, so the schema already explains both parameters. The description adds 'Needs PROXIMO_PBS_* config', which is more of a usage prerequisite than parameter semantics. It does not add specific parameter meaning beyond what the schema provides, so baseline 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 'get one PBS tape drive's config' with 'READ-ONLY', distinguishing it from sibling tools like pbs_tape_drive_list (multiple drives) and pbs_tape_drive_create/delete (mutation). The specific verb+resource makes 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 notes it is 'READ-ONLY' and requires 'PROXIMO_PBS_* config', giving clear context. It does not explicitly list alternatives (e.g., pbs_tape_drive_list for listing all drives), but the purpose is distinct enough to guide selection.

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