Cancel Hermes Toolkit job

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

The description discloses one important behavior: it is 'best-effort' and 'process-local', which conveys that cancellation may not always succeed and is scoped to in-process jobs. However, there are no annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false are all defaults), so the description carries the transparency burden. It does not disclose whether cancellation is reversible, what happens to the job's partial results, or whether re-running is possible afterward.

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 compact sentence that front-loads the purpose and key caveat ('best-effort', 'process-local'). There is minimal waste, although it could benefit from a sentence about parameter usage or when cancellation might fail.

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?

This is a mutating operation (cancellation) with an output schema and 4 parameters, 3 of which are undocumented at 0% schema coverage. The description does not explain the return value semantics, what 'best-effort' means operationally (e.g., could it return a failure status?), or the role of the optional parameters. Given the mutation nature and undocumented parameters, the description is not complete enough.

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% and the description only mentions 'job_id/run_id' parameter. It does not explain the semantics of the optional 'home', 'profile', and 'toolkit_root' parameters, which default to null and appear to configure the toolkit environment. An agent would not know why or when to supply these optional values to resolve a job to cancel.

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 specific action ('cancel') on a specific resource ('process-local Hermes Toolkit MCP async eval job') identified by job_id/run_id. This clearly distinguishes from siblings like hermes_api_jobs_cancel variants and hermes_skill_eval_start. However, the term 'best-effort' is somewhat ambiguous — it doesn't clarify what could prevent the cancellation.

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 this is for async eval jobs started by the MCP async mechanism, but provides no explicit when-to-use vs alternatives. Siblings like hermes_api_jobs_pause/resume and hermes_job_status exist, but no guidance is given on when to cancel vs pause, or whether this tool only works on the process-local MCP jobs versus the HTTP API jobs. No exclusions or alternatives are mentioned.

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