pbs_node_task_status

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

No annotations are provided, so the description carries the full burden. It explicitly says 'READ-ONLY', indicating no side effects. It lists the kind of data returned (status/exitstatus/pid/starttime/...) and mentions config requirement. However, it does not describe what happens if the UPID is not found or whether the call might fail silently.

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 two concise sentences. The first sentence front-loads the action ('READ-ONLY') and core purpose. The second sentence adds alternative tools and config requirement. No redundant or verbose phrasing.

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?

A simple read tool with an output schema (so return values are covered by schema). The description covers purpose, usage alternatives, configuration, and read-only nature. It does not clarify the node parameter behavior (default localhost) or mention error handling, but overall it is sufficiently complete for its complexity.

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 description coverage is 100% (all three parameters have descriptions in the schema). The tool description adds 'by UPID', confirming the key parameter, but does not add new semantics beyond what the schema provides. 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 starts with 'READ-ONLY' and clearly states 'get one PBS task's status by UPID'. It lists specific attributes (status/exitstatus/pid/starttime/...) and distinguishes from siblings by mentioning pbs_tasks_list for finding UPIDs and pbs_node_task_log for the full 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?

Explicitly tells when to use (get status by UPID) and provides alternative tools for related tasks (pbs_tasks_list to find UPIDs, pbs_node_task_log for full log). Also notes configuration prerequisite ('Needs PROXIMO_PBS_* config'), which guides proper usage.

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