dsh_rename_workspace

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

With no annotations, the description carries the full burden, and it does disclose the highest-risk behavioral fact: this changes only the sidebar title and does not move the folder. It omits other traits an agent might want, such as permission requirements, idempotency, or what happens when the identifier does not resolve.

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 a clarifying parenthetical; every clause earns its place and nothing is padded.

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?

No output schema is needed for a rename, and the schema fully documents the arguments, so the description covers what is required to call it correctly. The one unresolved point is how the workspace is identified when only 'title' is marked required, which neither the schema nor the description clarifies.

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 baseline is 3. The sentence 'Identify it by workspace_id or path' restates the identifier parameters rather than adding format, constraint, or precedence rules (e.g. which wins if both are supplied).

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?

Specific verb+resource ('Rename a DeepSeek Harness workspace') with an immediate scope qualifier ('sidebar title only; the folder is not moved'). The workspace vs. session distinction is implicit in the name, so an agent can separate it from the sibling dsh_rename_session.

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 parenthetical exclusion ('the folder is not moved') sets a clear expectation boundary, and 'Identify it by workspace_id or path' tells the agent how to target the tool. It does not, however, name an alternative tool or state prerequisites, so it stops short of full when/when-not routing.

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