dsh_open_session

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

No annotations are provided, so the description carries the full burden. It usefully discloses the reuse-matching semantics and the override, but says nothing about side effects (does it spawn a process?), failure modes when cwd is invalid, permissions/auth, or whether reopening affects existing sessions.

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?

Three short sentences, zero waste, with the primary action and default behavior front-loaded before the override instruction.

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 exists, and the description never indicates what opening a Session returns (presumably an identifier an agent needs for dsh_send / dsh_read). For a tool at the entry point of a session workflow, that return-value gap plus missing failure semantics leaves it only partially 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 coverage is 100%, so all three parameters are documented. The description adds context only for 'reuse' (matching rule, override), while cwd and preset are essentially restatements of the schema, so 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?

States a specific verb and resource ('Open a Session in the running app'), and the resource is distinct from every sibling (list/send/wait/read/cancel), so an agent can route confidently.

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?

Clearly explains the default behavior (reuse newest idle Session with same preset and cwd) and the condition for opting out ('Set reuse to false for a new Session'). Lacks guidance on when to prefer checking dsh_list_sessions first or what to do when no idle session matches.

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