Run a health check on your DeepSeek Harness setup to identify and resolve issues with the DSH binary, settings.yaml, model endpoint connectivity, and Web UI status.
Health-check the DeepSeek Harness setup. Checks DSH binary installation, ~/.dsh/settings.yaml configuration, model endpoint connectivity, and Web UI status.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of disclosing behavior. It explicitly lists what the tool checks and implies a read-only diagnostic nature. It stops short of stating side effects or output behavior, but for a health-check tool the listed scope is meaningful.
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 and then usefully enumerates the check scope. Every element contributes information, with no filler or redundancy.
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 zero-parameter diagnostic tool with no output schema, the description gives enough context to select and invoke it correctly. It does not describe the format of the health-check result, which would be useful but is not essential for tool selection.
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?
The tool has zero parameters, so the schema is inherently complete. There is no parameter semantics burden for the description to carry, and the baseline of 4 applies.
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 starts with a clear verb, 'Health-check', and names the specific resource, 'DeepSeek Harness setup'. It enumerates the exact components checked (binary installation, settings.yaml, model endpoint connectivity, Web UI status), which distinguishes it from narrower siblings like dsh_web_status.
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 guidance is given on when to use this tool versus alternatives. The agent must infer that this is the general diagnostic entry point, and the description does not explicitly distinguish it from dsh_web_status or say when a narrower sibling would be preferable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.