bw_processchain_check

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

There are no annotations, so the description must carry the behavioral burden. 'Check' implies a read-only validation, but the description does not say whether it mutates anything, what 'consistency' means, whether it performs a remote call, or what happens if the chain is inconsistent. This is a meaningful transparency gap.

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 a single efficient sentence with no wasted words, but it is under-specified rather than appropriately concise. It front-loads the core operation but lacks the details expected for a tool with no annotations or output schema.

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?

With no output schema and no annotations, the agent has no idea what the tool returns (boolean, issue list, status) or what constitutes a failed check. It also lacks prerequisites and side-effect information, leaving the context incomplete for reliable invocation.

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 coverage is 0% and the description never mentions the required id parameter. The parameter name is inferable from the tool name, but the description adds no format guidance, source for the ID, or meaning beyond the bare schema field.

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 uses a clear verb-resource pair: 'Check' + 'process chain consistency', so an agent can tell this is a validation/check operation rather than an execution or detail fetch. However, 'consistency' is not defined and there is no explicit contrast with sibling tools like bw_processchain_details, so the differentiation is only partial.

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 no guidance on when to call this tool versus alternatives such as bw_processchain_execute, bw_processchain_logs, or the other *_check tools. An agent cannot infer prerequisites (e.g., process chain must exist, connection required) or whether this should precede execution.

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