pbs_job_delete

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

With no annotations, the description carries full burden and excels. It labels the tool as MUTATION, explains dry-run behavior, the role of confirm, and explicitly states that backup data is NOT deleted. It also mentions configuration prerequisites.

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?

Extremely concise: two sentences with no wasted words. Every piece of information is essential and front-loaded.

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 output schema exists, the description covers key aspects: purpose, mutation nature, dry-run, effects on schedule and backup, and config requirement. It does not mention required parameters explicitly (job_id and job_type are required) but overall is sufficiently complete.

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 only 25%, but the description adds value by specifying valid job_type values and explaining the confirm parameter (dry-run by default, confirm=True to execute). It does not detail job_id or proximo_target further, but the schema describes the latter.

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 it deletes a PBS scheduled job with specific verb and resource. It mentions job_type values (sync|verify|prune), distinguishing it from sibling tools like pbs_job_create or pbs_job_update.

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?

Provides clear context for use: deleting scheduled jobs, dry-run by default, and the need for PROXIMO_PBS_* config. However, it does not explicitly state when not to use it or compare to alternatives.

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