job_cancel

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

With no annotations, the description carries the full burden of behavioral disclosure. It honestly states that the subprocess is terminated, implying irreversibility, but does not mention what happens if the job is not running, whether cancellation is asynchronous, or any side effects on job status. It adds useful context but is not comprehensive.

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 with a parenthetical clarification. Every word is useful, the action is front-loaded, and there is no redundant or filler text. It is appropriately concise for 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?

For a one-parameter tool with no output schema and no annotations, the description provides the core action and effect but lacks guidance on locating job_id and handling edge cases like already-completed jobs. It is adequate for simple usage but has clear gaps in completeness.

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. It does not explain job_id beyond its name, nor does it mention how to obtain it (e.g., via job_list). The description adds no parameter-specific meaning, which is a gap for a required parameter.

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 uses a specific verb 'Cancel' and a clear resource 'running background job', while the parenthetical 'terminates its subprocess' adds precise behavioral detail. This distinguishes it from sibling tools like job_status and job_list, which concern querying rather than mutating jobs.

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 clearly indicates that this tool applies to 'running' background jobs, which provides context for when to use it. However, it does not explicitly name alternatives or mention exclusions, such as 'use job_list to find job_ids' or 'not for completed jobs', though the target context is reasonably clear.

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