stop-simulator-server

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

With no annotations present, the description carries the full behavioral burden and does so thoroughly. It discloses the silent-failure behavior, the return shape, platform-specific resource cleanup (including TV daemon reaping), what is deliberately left running on iOS/Android/TV, and the Chromium-specific cascade where the CDP session and console history are terminated.

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?

Although longer than average, every sentence earns its place by covering a distinct aspect: core action, usage trigger, exclusions, platform exception, return value, and failure mode. The information is logically ordered and front-loaded with the primary purpose before caveats.

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 multi-platform complexity, no output schema, and no annotations, the description is remarkably complete. It explains what happens per platform, what is preserved, what is destroyed, how to reconnect if needed, what is returned, and how failure behaves. An agent has enough information to select and invoke this tool correctly.

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 already provides 100% parameter coverage: the single required `udid` is described as 'Target device id (iOS UDID, Android serial, or Chromium id) whose transport session to stop.' The description adds only the phrase 'given id' and the context that it refers to a specific device, which matches the schema rather than extending it. Baseline 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 states a specific verb ('Stop') and resource ('transport session for a specific device') and immediately disambiguates across iOS, Android, physical iOS, Chromium, and TV. It clearly differentiates from the sibling stop-all-simulator-servers by emphasizing 'specific device' while keeping others running.

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?

Explicit usage guidance is provided: use when done with one device but want to keep others alive, or to restart a wedged transport. It also gives an explicit exclusion and alternative—use stop-all-simulator-servers with `devices` to drain native-devtools, accessibility, profiler, and debugger services on iOS/Android/TV.

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