pbs_tape_backup_job_get

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

No annotations provided, so description carries full burden. It states read-only and trusted, but does not disclose error behaviors (e.g., invalid job_id), required permissions, or performance characteristics. Minimal insight beyond safety.

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?

Description is very concise (one line) with key prefixes (READ-ONLY, REVIEWED_TRUSTED) and content upfront. No unnecessary text, though slightly terse.

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?

For a simple retrieval tool with a clear schema and output schema, the description covers core aspects: purpose, safety, and configuration need. Does not reiterate output schema, which is appropriate.

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% and already describes both parameters (job_id and proximo_target) adequately. The description adds no extra semantic value beyond what the schema provides.

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 retrieves a single PBS tape backup job's full config, distinguishing it from sibling tools like pbs_tape_backup_job_list (for listing) and mutation tools like pbs_tape_backup_job_create.

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 'REVIEWED_TRUSTED' and 'Needs PROXIMO_PBS_* config', which implies it is safe and requires configuration, but lacks explicit when-to-use guidance compared to alternatives like the list or update tools.

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