dsh_create_session

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does reveal a key side effect ('auto-creates the workspace if missing') and the return value (sessionId), but omits potential error conditions, permission requirements, or whether the operation is safe/idempotent beyond auto-creation.

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 two sentences, front-loaded with the core action, and every word adds value—no filler or redundant phrasing.

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 tool with 0 required parameters and full schema coverage, the description explains the core behavior (auto-create workspace) and output (sessionId), linking it to follow-up calls. It lacks error-handling or prerequisite details, but the essentials for correct invocation are present.

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 input schema covers 100% of parameters with meaningful descriptions (model, provider, workspace_path, reasoning_effort). The description reinforces workspace_path's role with 'bound to a directory' but adds minimal new meaning beyond the schema, so the baseline of 3 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 clearly states the verb 'Create' and the resource 'a new DSH session' bound to a directory, with the additional behavior 'auto-creates the workspace if missing' and the return value 'sessionId'. This distinguishes it from siblings like dsh_resume_session (resume) and dsh_list_workspaces (list).

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 positions the tool as the entry point for starting a new session, noting it 'Returns the sessionId for follow-up tool calls', implying use before dsh_send_message or dsh_get_session_stats. It does not explicitly name alternatives or exclusions, but the word 'new' and the sibling names make when-to-use clear.

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