Submit and dispatch batches of one-shot or long-lived jobs to SSH-connected Arch Linux drones, enabling parallel agent tasks with log retrieval and cancellation.
Submit and, by default, dispatch one-shot or long-lived jobs as a batch.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry full behavioral burden. It only states submit/dispatch and mentions a default, but omits permissions, side effects, long-lived job semantics, cancellation behavior, and batch error handling.
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?
A single, front-loaded sentence with no filler. It is efficient, though arguably too sparse for a batch dispatcher.
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 batch job dispatch tool with no annotations, no output schema, and many related siblings, one sentence is not enough. It lacks prerequisites, return expectations, and side-effect disclosure.
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 reported at 100%, so the baseline is 3. The description gestures at 'jobs' and 'batch' but does not clarify agent_id, job structure, or dispatch control beyond what the schema already provides.
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+resource: submit and dispatch jobs as a batch. The default dispatch behavior is useful, but it does not distinguish itself from siblings like dispatch_pending or promote_persistent.
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?
No explicit when-to-use guidance or alternatives are given. The phrase 'by default' hints at a dispatch/not-dispatch option, but there is no routing advice against sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.