dsh_delegate

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

The description adds meaningful behavioral context beyond the annotations: it states the tool creates a session (mutation), uses DSH's configured model (so no model parameter), and is detached by default. The annotations only provide false hints, so this extra information is valuable, though it does not cover return behavior or session identification.

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 three concise sentences with no filler or repetition. It front-loads the core purpose and adds only high-signal details about model usage and detachment.

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?

Given six parameters and no output schema, the description is incomplete. It does not explain what the tool returns (e.g., session ID), how to interact with the created session, or the meaning/effects of parameters like waitSeconds or workspaceMode. The lack of annotation guidance further burdens the description, which it does not fully carry.

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 only 17%, with only 'cwd' described in the schema. The description does not explain any of the six parameters (prompt, title, agentPreset, waitSeconds, workspaceMode). The note about 'no model argument accepted' is a constraint, not a parameter explanation, and 'cwd' is already covered by 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 a specific action: 'Create a root session on the configured official DSH Web Host and queue the initial prompt.' It also differentiates from siblings by noting 'no model argument is accepted' and 'Detached by default,' which sets it apart from follow-up or observation tools.

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 clearly conveys when to use it: for creating a root session and queuing the initial prompt. It implicitly indicates it is the entry point for a session, distinguishing from siblings like dsh_followup or dsh_continue, but it does not explicitly state exclusions or when not to use it.

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