pi_stop

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

Annotations already mark destructiveHint=true and readOnlyHint=false, and the description adds valuable behavioral context: 'PixInsight stays open' for daemon, 'loses unsaved windows' for kill, and the unique capability to abort ImageIntegration. This goes well beyond what the annotations alone provide.

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?

Single sentence, front-loaded action, and a parenthetical that packs both consequence and exception into minimal space. Every word 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 one-parameter tool with strong annotations and no output schema, the description covers the action, the two modes, the key safety hazard (unsaved windows), and a special use case (aborting ImageIntegration). Nothing an agent needs to call it correctly is missing.

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?

With 0% schema description coverage, the description carries the semantic burden. It explains the 'kill' mode effect and contrasts it with daemon mode; the default value is left to the schema, but no critical parameter meaning is missing.

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 distinguishes two resources: the daemon loop and the PixInsight process. It also makes the mode distinction explicit, so an agent can tell what this tool does without opening the 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?

The description gives clear context: daemon mode stops the loop while keeping PixInsight open, and kill mode is 'the only way to abort a running ImageIntegration.' It doesn't explicitly name sibling alternatives like pi_restart, but the when-to-use guidance is strong enough to route an agent.

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