pbs_list_tasks

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is clear. The description adds useful behavioral context by stating that running or failed tasks come with their full UPID, which aids follow-up. It does not contradict annotations.

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 is two sentences, front-loaded with the action 'Browse recent PBS tasks', and every clause adds value. No redundant or filler content.

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 and thorough annotations, the description covers the essential context: the purpose, available filters, and how results relate to follow-up tools. It is complete for a list-style 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?

The schema descriptions fully document each parameter (limit, running, typefilter, errors_only), so the description does not need to duplicate them. The description does offer a high-level summary of the filters, but adds no new semantics beyond the schema. Thus 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 the tool's function: 'Browse recent PBS tasks' with optional filters. It explicitly names the resources (tasks) and verbs (browse), and distinguishes itself from sibling tools by noting that UPID is provided for follow-up via pbs_get_task_status / pbs_get_task_log.

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 implies usage context: it's for listing tasks, and the mention of follow-up tools suggests when you might use this (to obtain UPIDs for status/log lookups). However, it does not explicitly state when not to use it or compare directly with alternatives like pbs_list_verify_jobs.

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