terminate_simulator

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

With no annotations, the description carries the full burden and does meaningful work: it limits scope to ConnectIQ.app only, clarifies that stored data survives, and prescribes verifying stopped status before relaunch. It stops short of describing behavior when no simulator is running or what a failed termination looks like.

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?

Three short sentences with the scope constraint front-loaded, then the parameter caveat, then the follow-up action. No filler and no repetition of structured data.

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 one-parameter, non-destructive teardown with no output schema and no annotations, the description covers scope, side effects, and next steps. The mention of 'confirming stopped status' implies a status signal without explaining how to check it, which is the remaining gap.

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 single parameter has 0% schema description coverage, so the description must supply meaning, and it does: `force` is explicitly tied to an unresponsive simulator. It omits the default of false and what non-forced termination does if the app is hung, leaving a small gap.

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?

Names a specific verb (terminate) and a specific target (ConnectIQ.app), and the word 'only' scopes the operation against broader shutdown behavior. It is distinguishable from siblings like stop_app in practice, though it never explicitly contrasts itself with them.

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?

Gives a clear condition for the `force` variant (unresponsive simulator) and sequence guidance ('relaunch separately after confirming stopped status'). It does not name an alternative tool or state when not to use this one, so the 5-level bar of explicit alternatives is not met.

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