dsh_runtime_unload

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

With no annotations, the description must carry the disclosure burden. It does disclose the destructive nature (remove and restart) and the --allow-runtime requirement, but it omits other behavioral context such as impact on active sessions, dependencies, or reversibility. The core behavior is transparent, but depth is limited.

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 short sentences, front-loaded with the action, and contains no filler. Every phrase earns its place, making it highly concise and well-structured.

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 simple tool with one parameter and no output schema, the description is fairly complete. It states the action, the target resource, and a key prerequisite. It could mention failure modes or effects on other packages, but these are not essential given the tool's simplicity.

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 schema provides only a property name 'packageName' with no description (0% coverage). The description's phrase 'Remove a package' implies that packageName identifies the package to remove, but it does not explicitly map the parameter or clarify format or semantics. The parameter is self-explanatory from context, but the description could add more value.

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's purpose: 'Remove a package from the live profile and restart the DSH runtime.' It uses a specific verb ('Remove') and resource ('package from the live profile'), and the restart action distinguishes it from sibling tools like load, start, and stop.

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 provides a prerequisite ('Requires --allow-runtime') but gives no guidance on when to use this tool versus alternatives such as dsh_runtime_load or dsh_runtime_stop. It does not mention exclusions or scenarios where another tool would be more appropriate.

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