rh_job

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

With no annotations, the description carries the full burden. It adds one specific behavioral trait: it will not hide provider errors and will not retry an uncertain submit. However, it omits other key behaviors such as permissions needed, side effects of cancel/resume, idempotency, or timeout semantics. The one disclosed behavior is useful but insufficient.

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 a single sentence, which is concise, but it is front-loaded with purpose and then tacks on a behavioral caveat. It lacks structural separation between what the tool does and how it behaves, making it somewhat cryptic for a 4-action tool.

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 4 parameters, 0% schema coverage, no annotations, and no output schema, the description is far too thin. It states purpose and one behavior but leaves action semantics, parameter meanings, and return expectations unexplained. An agent would struggle to invoke this correctly without opening the schema.

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 0% for 4 parameters, so the description must compensate. It provides no meaning for the action enum values, job_id, timeout_ms, or provider_task_id. The agent gains no semantic guidance beyond the raw schema constraints (enum, minLength, pattern).

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 states a clear verb-resource pair: 'inspect or advance one durable job.' This distinguishes it from most siblings (which handle workflows, models, assets), but it does not explicitly name or contrast with any specific sibling. The enum actions are not mentioned, though the overall purpose is clear.

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?

There is no explicit when-to-use guidance, no when-not-to-use conditions, and no alternatives named. The phrase 'without hiding provider errors or retrying an uncertain submit' is a behavioral constraint, not usage guidance. An agent must infer when to call this tool versus others.

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