pbs_admin_prune_jobs_list

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

Declares read-only and mentions 'job comment/schedule' in parentheses, but details on exact output or side effects are minimal. Without annotations, more description of behavior would be beneficial.

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 concise sentences with key info front-loaded (READ-ONLY). No wasted words.

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?

Sufficient given output schema exists. Mentions config requirement and precedent, but missing the store filter parameter context. Still adequately complete for a simple list 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 covers both parameters with descriptions (100% coverage). Description adds no extra parameter meaning beyond what schema already provides, so baseline score applied.

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 view of prune jobs, distinguishing it from siblings like pbs_admin_gc_jobs_list and pbs_jobs_list. Mentions matching pbs_jobs_list precedent, reinforcing specificity.

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 how to trigger a prune job manually via pbs_job_run, and notes the config requirement. Lacks explicit exclusions but provides clear context for when to use this tool vs. alternatives.

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