bw_processchain_stop

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly warns that the action is irreversible, which is essential for a stop operation, but it does not describe side effects on running jobs, logs, or subsequent scheduling.

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?

The description is extremely concise: two short sentences, no filler, and the key scoping and risk information is front-loaded. 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?

The tool is structurally simple with one string parameter and no output schema, so the description does not need to explain much. Still, the id semantics are undocumented and there is no mention of return or failure behavior, making it adequate but not fully self-contained.

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?

Schema description coverage is 0% and the description never mentions the 'id' parameter. The tool name and context let an agent infer that id likely identifies the process chain to stop, but the format, whether it is a run instance id, and any constraints remain 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') and a specific resource ('running process chain'), and it is the only stop-oriented tool among the siblings. It is clearly distinguishable from bw_processchain_execute, bw_processchain_check, and bw_processchain_logs.

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 phrase 'running process chain' implies that the tool is for active executions and provides some contextual guidance. However, there are no explicit when-not-to-use conditions, no alternatives are named, and there is no guidance on how the chain should be identified before stopping.

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