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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds routing information only and says nothing about process lifecycle — whether the process keeps running after the call, that output must be retrieved via read_process_output/interact_with_process, or that kill_process/force_terminate are needed to stop it — which would have been genuinely useful context for a destructive, open-world tool.

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?

Two sentences, no filler: the when-to-use condition is front-loaded and the alternative-tool list follows immediately. The length is justified because each named sibling represents a distinct routing decision.

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?

An output schema exists, so return values need not be explained, and routing across the large sibling set is thorough. The remaining gap is process lifecycle semantics (background execution, how long it lives, how to stop it), which the agent must infer from sibling names like wait_for_process_output and kill_process.

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%: device, command, and timeout_ms are each documented in the schema (including the 1000 ms default). The description adds no parameter-level detail such as command syntax, shell used, or working-directory behavior, so the baseline 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 states a specific action (run a shell command, build, test suite, script, or terminal server) and explicitly frames it as the fallback tool for command execution when no narrower semantic tool applies. An agent can distinguish it from all eight named alternatives without opening another schema.

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?

It gives an explicit when-to-use condition plus a one-to-one routing map for every competing tool (launch_app for GUI, service for service manager, power_action for power, network, event_log, installed_apps, environment, open_path/reveal_path). Nothing is left to inference.

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