artwork_job_run

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 does not disclose whether execution is blocking or asynchronous, how long an AI-driven job may run, whether it mutates documents irreversibly, or whether it consumes provider credits — all material for an execution tool.

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?

A single front-loaded sentence with no filler, stating the action first and the execution mechanism second. Nothing wasted, though it is arguably too terse given the missing behavioral detail.

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?

An output schema exists so return values need not be described, but for an execution tool with no annotations the definition omits prerequisites, async/blocking behavior, and failure conditions — the agent cannot call it confidently without opening sibling tools.

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%, so the description must compensate and does not: job_id is never mentioned or characterized (format, source, whether it must reference a paused job). The name is largely self-evident from sibling tools, which keeps this above a 1.

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?

States a specific verb+resource ('Run a queued/paused artwork job') plus the execution channel (AI provider and semantic GIMP tools). It is reasonably distinguishable from artwork_job_create/status/pause/resume/cancel siblings, though it does not explicitly name them.

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 qualifier 'queued/paused' implies the precondition that the job must already exist in one of those states, but the description never says when to choose this over artwork_job_create, resume, or followup, nor what happens if the job is in another state.

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