pbs_admin_verify_jobs_list

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

Declares READ-ONLY, indicating no destructive effects. Also notes requirement for PROXIMO_PBS_* config. With no annotations provided, this provides adequate transparency for a list operation.

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?

Three sentences, each adding essential information. Front-loaded with purpose and read-only status. No redundant or extraneous text.

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 tool simplicity (list with two optional filters), description covers purpose, usage guidance, and prerequisites. Output schema exists for return values, so no additional explanation needed.

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 both parameters are well-documented in the schema. The description adds no additional parameter-specific information, maintaining baseline for high schema coverage.

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?

Clearly states it is a READ-ONLY job-level view of verification jobs, distinguishing it from other admin job list tools (gc, prune, sync) and from triggering tools like pbs_job_run.

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?

Explicitly tells user to use pbs_job_run to trigger a verification manually, and mentions a configuration prerequisite. However, it does not explicitly compare with other admin job list tools.

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