artwork_job_resume

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

With no annotations, the description must carry the behavioral burden. It usefully discloses that this only clears a flagged state and does NOT itself resume execution, which prevents a misuse. However, it omits permissions, idempotency, and behavior when the job is not paused or does not exist.

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?

Two short sentences, zero waste, with the core action front-loaded and the follow-up chained immediately after. Sized exactly to the tool's simplicity.

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 explained. For a one-parameter state-clearing tool, the description covers the action and the required follow-up call; only the precondition and error behavior are unstated.

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 the single required job_id parameter, and the description says nothing about the identifier's format or source (e.g., from artwork_job_list or artwork_job_create). The meaning is largely inferable from the name, but the description does not compensate for the coverage gap.

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 and resource: 'Clear the pause flag for an artwork job.' This cleanly distinguishes it from siblings artwork_job_pause (sets the flag) and artwork_job_run (executes), so an agent can route without opening either schema.

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?

Gives a clear next-step instruction ('Call artwork_job_run to continue execution'), which defines the tool's place in the workflow and names the alternative action. It does not explicitly state the precondition (the job must currently be paused) or what happens if it is not, so it falls short of full when/when-not guidance.

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