dsh_runtime_load

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

With no annotations, the description carries the full burden of disclosure. It does mention the runtime restart, a notable side effect, and the permission requirement. However, it omits details about downtime, persistence, error conditions, or reversibility.

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 a single concise sentence, front-loaded with the core action. However, it is under-specified in a way that hurts usability, so the brevity is not optimally balanced with necessary information.

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 the tool's action (install + restart) and an opaque 'spec' parameter, the description is incomplete. It does not explain the parameter, return behavior, or when to use this over sibling tools, leaving significant gaps for the agent.

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 only parameter 'spec' has no schema description and the tool description does not mention it at all, leaving the agent completely uninformed about expected format, values, or purpose.

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 tool installs an additional plugin into the live profile and restarts the DSH runtime, which gives a specific verb and resource. It somewhat distinguishes from dsh_plugin_install by mentioning the runtime restart, but does not explicitly name sibling 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?

No guidance is provided on when to use this tool over alternatives like dsh_plugin_install or dsh_runtime_unload. The only usage-related note is the prerequisite 'Requires --allow-runtime', which is a constraint but not a contextual recommendation.

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