ksp_flight_guidance_stop

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

With no annotations, the description carries the full behavioral burden. It discloses that MCP control is released and that the tool serves as a safety exit, which is useful context beyond the name. It does not say whether the guidance plan is discarded or resumable, whether the craft stays under manual control afterward, or how it behaves if no plan is active.

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, zero filler, with the action front-loaded and the usage conditions immediately after. Every clause earns its place.

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 zero-parameter, annotation-free stop tool, the description covers purpose, effect (control release), and trigger conditions adequately. The remaining gap is post-stop state and no-op/error behavior, which is minor here.

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 tool takes zero parameters, so the baseline is 4 and there is no parameter semantics for the description to add. Nothing is misstated or left ambiguous.

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?

States a specific verb ('Stop') and resource ('the active closed-loop guidance plan') plus a second effect ('release MCP control'), so an agent knows exactly what it does and can tell it apart from ksp_flight_guidance_start. It does not, however, distinguish itself from adjacent siblings like ksp_flight_abort or ksp_flight_clear_control, which an agent might reasonably confuse it with.

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 concrete triggering conditions: timeout, flameout, commandability loss, or explicit human takeover, framed as 'the AI safety exit'. That is real when-to-use guidance. It stops short of naming when NOT to use it or which sibling to prefer for abort/control-clear scenarios.

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