Start the DeepSeek Harness Web UI as a background daemon on port 3080, providing a browser interface to manage autonomous coding and dual-agent verification.
Start the DeepSeek Harness Web UI companion in background daemon mode on port 3080 (http://127.0.0.1:3080).
| Name | Required | Description | Default |
|---|---|---|---|
| port | No | Port to bind (default: 3080). |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden. It adds useful context: background daemon mode and the exact URL/port. However, it does not disclose what happens on startup failure, whether the command is idempotent, or whether it returns immediately (though daemon mode implies it). This is more than a bare 'start' but leaves important behavioral gaps.
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 sentence that front-loads the action, mode, and address. No filler, every phrase earns its place. The URL is included as a compact operational detail.
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?
Given the tool's low complexity (one optional parameter, no output schema, no annotations), the description is largely sufficient for correct invocation. It covers purpose, mode, and endpoint. The main missing piece is usage guidance, but that was already scored in its own dimension; for the given complexity, the description is mostly complete.
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% for the single optional 'port' parameter, which already documents the default (3080). The description mentions port 3080 but adds no new semantics beyond the schema. Per calibration, 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 states a specific verb ('Start'), a clear resource ('DeepSeek Harness Web UI companion'), and precise operational details (background daemon mode, port 3080, URL). This distinguishes it from siblings like dsh_web_status, dsh_web_stop, and dsh_run_task without requiring schema inspection.
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 does not provide explicit guidance on when to use this tool versus alternatives like dsh_web_status or dsh_web_stop. It implies usage (start the UI) but offers no exclusions, prerequisites, or mentions of sibling tools. An agent must infer when this is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.