Resume asynchronous mission

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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds meaningful behavioral context: resuming creates a new job_id rather than continuing the old one, and it preserves the goal, roles, criteria, and remaining iterations. This is valuable beyond the annotations.

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, focused sentence that front-loads the key behavior (resume) and then specifies what is preserved. No wasted words.

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?

For a single-parameter tool with full schema coverage and no output schema, the description is largely complete. It explains the key side effect (new job_id) and what is carried over. It could mention that the original paused job remains unchanged or that the new job must be tracked, but this is a minor gap.

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 100%, so the schema already documents the job_id parameter. The description doesn't add additional parameter-level detail beyond what the schema provides, but it does clarify that the job_id refers to a paused job. Baseline 3 is appropriate.

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 verb 'Resume' and the resource 'a paused job', and it specifies that it creates a new job_id with the same goal, roles, criteria, and remaining iterations. It distinguishes itself from mission_pause and mission_cancel, though it doesn't explicitly name a sibling alternative.

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 description implies the tool is for resuming paused jobs, which is clear context. However, it doesn't explicitly state when to use this tool versus alternatives like mission_claim or mission_release, nor does it mention prerequisites such as the job being in a paused state.

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