Create or open a DeepSeek Harness workspace

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

With no annotations provided, the description carries full burden. It discloses key behaviors: never overwrites existing files, safe reuse, auto-start/connect, and web-transport-specific workspace creation. It also details return fields, providing transparent expectations.

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 well-organized paragraph that front-loads the core purpose and then details behaviors and returns. Every sentence adds value, with no filler.

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 description covers the main return values and behavioral nuances, including web transport specifics. It doesn't mention error conditions or prerequisites, but given the tool's complexity and lack of output schema, it provides sufficient context for correct invocation.

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%, so the schema already documents both parameters. The description reiterates the absolute path requirement and open_browser's web-mode control but doesn't add substantive new meaning beyond the schema.

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 clearly states the tool's function: create or reuse a DSH session for a given directory, with explicit behaviors like directory creation, safe reuse, and no overwriting. It distinguishes itself from siblings like dsh_start (service startup) and dsh_session (session management) by focusing on workspace establishment.

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 usage for establishing/reusing a workspace, but it doesn't explicitly compare with sibling tools or state when NOT to use it. It mentions auto-starting DSH when necessary, but gives no guidance on choosing this over dsh_start or dsh_session.

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