launch_stop

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=true), the description adds that the call closes the launch window and returns { stopped }. It does not contradict the annotations and provides useful lifecycle context.

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 short sentences carry all the needed information: purpose, effect, return value, and when not to use it. Every phrase earns its place, and the 'When NOT to use' guidance is clearly separated.

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 no-parameter tool with no output schema, the description fully covers the operation, its lifecycle role, return value, and the common misuse case. An agent selecting among the runtime siblings has enough to invoke and reason about launch_stop 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?

There are zero parameters, so the description cannot add much beyond the empty schema. Per the 0-parameter baseline, a 4 is appropriate; nothing is undocumented.

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 names a specific verb ('Stop'), a specific resource ('the running Launch instance started by launch_start'), and the concrete effect ('closes the launch window'). This clearly distinguishes the tool from launch_start and the rest of the runtime workflow.

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 when-not guidance is provided: 'there is no need to call this between captures — keep the instance running and re-capture.' This routes the agent away from stopping and toward re-capturing, which is an explicit alternative behavior. The paired use with launch_start is also clear.

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