dsh_runtime_start

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

With no annotations provided, the description carries the full burden and does well by stating concrete side effects: it installs plugins, spawns a profile process, and bridges tools. It also discloses the required `--allow-runtime` flag, which is a permission-related behavior. The main gap is not mentioning reversibility or what happens to the existing profile state.

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 with no fluff. It front-loads the main action and packs in the prerequisites and bridge behavior efficiently. The phrase 'this MCP bundle' is slightly vague but not wasteful.

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 one optional parameter and no output schema, the description covers the essential operational sequence: install, spawn, bridge, and permission. It does not discuss return values or when to use, but given the moderate complexity and absence of structured schemas, it is reasonably 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 description coverage is 100%—the plugins parameter is fully described as 'github:owner/repo specs to install before boot'. The description merely refers to 'optional plugins' without adding new meaning, so the baseline of 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?

The description clearly lists three distinct actions: installing the MCP bundle and optional plugins, spawning `dsh --profile`, and bridging ctx.tools as dsh__* MCP tools. This is a specific verb+resource combination that differentiates it from sibling tools focused on plugin management or runtime loading.

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?

No explicit guidance is given on when to use this tool versus alternatives like dsh_runtime_load or dsh_plugin_install. The only stated condition is the prerequisite `Requires --allow-runtime`, but there is no mention of when this tool is the appropriate choice or when it should be avoided.

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