Submit a cancellable Hermes job

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

With only openWorldHint as an annotation, the description must carry behavior disclosure. It reveals the asynchronous behavior ('return immediately') and the mode-conversion behavior for execute requests. It does not cover cancellation or result retrieval, but the most important behavioral traits are disclosed.

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 sentences with no filler, and the core behavior is front-loaded. Minor deduction for jargon like 'approval-preview job' which is not defined, but overall it is efficient.

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?

The tool has 8 parameters, no output schema, and no parameter-level descriptions, so the description needs to be more complete to support correct invocation. It does not explain how results are obtained, what contextFiles does, timeouts, or how the created job can be cancelled, despite the title advertising cancellability.

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 for the 8 parameters. It only clarifies mode-related behavior and leaves model, preset, maxTurns, provider, contextFiles, and timeoutSeconds undefined. This is a significant gap for a tool with multiple functional options.

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 ('Start') on a clear resource ('long Hermes plan, draft, or approval-preview job') and explicitly notes it returns immediately. It also differentiates itself from sibling tools by explaining that execute mode is converted to request-approval rather than executed directly.

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 gives explicit routing guidance: execution should not go through this tool directly; instead, use hermes_prepare and hermes_approve for execution. This clearly tells an agent when to use this tool versus the alternatives.

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