pbs_job_create

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

Labels as MUTATION, explains dry-run default, and clarifies 'Config-only; no existing data affected.' No annotations provided, so description carries full burden and provides useful behavioral context.

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?

Very concise, front-loaded with key info (MUTATION), and no unnecessary words. Every sentence adds value.

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 low parameter coverage, no annotations, and many siblings, the description is incomplete. It does not explain output, scheduling behavior, or how this tool relates to pbs_job_run/update.

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?

Only explains job_type values and confirm behavior. With 13% schema coverage and 8 parameters, the description fails to compensate for the lack of schema documentation for most parameters.

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 action (create) and resource (PBS scheduled job), and mentions job types. It distinguishes from siblings via the 'create' verb, but does not explicitly differentiate from pbs_job_run 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 guidance on dry-run and confirmation, and mentions config dependency. However, it lacks when-not-to-use and alternatives among siblings.

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