pbs_tape_backup_job_list

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

With no annotations provided, the description carries the full burden. It clearly labels the tool as 'READ-ONLY' (no side effects) and identifies the source of the jobs as 'REVIEWED_TRUSTED: operator-authored scheduled-job config', adding valuable behavioral context beyond the schema.

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 consists of three short, information-dense sentences. Every sentence adds value: purpose, trustworthiness, and configuration requirement. No redundancy or 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?

Given the presence of an output schema, the description adequately covers the tool's purpose, read-only nature, config requirement, and data source. It does not mention pagination or empty results, but for a simple list tool this is sufficient.

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 the description does not add any additional meaning about the single optional parameter ('proximo_target') beyond what the schema already provides. 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 action ('list') and the resource ('configured PBS tape backup jobs'), distinguishing it from similar tools like pbs_tape_backup_job_create or pbs_jobs_list. The 'READ-ONLY' prefix reinforces the purpose.

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 the prerequisite 'Needs PROXIMO_PBS_* config', but does not explicitly contrast with alternative tools or provide when-not-to-use guidance. The 'READ-ONLY' labeling indirectly implies it is for viewing, but no explicit exclusions are given.

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