Pause, resume, or suspend a MELRA workflow

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), but the description adds genuinely useful behavioral context: node state is preserved and a resumed workflow continues from where it stopped, which is the key non-destructive guarantee an agent needs. It still omits auth requirements or whether halting affects in-flight nodes.

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 tight sentences, front-loaded with the core action and the state-preservation guarantee; no filler.

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?

Annotations carry the safety profile and there is no output schema, so the remaining burden is action semantics — which the description leaves incomplete. An agent can call the tool, but cannot reliably choose between pause and suspend from the definition alone.

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 adds no parameter meaning: it never explains the action enum values (pause/resume/suspend) or what workflowId refers to. The phrase 'halt... or lift a halt' only loosely implies two of the three enum options, leaving the distinction between pause and suspend undefined.

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 general verb+resource ('Halt a running workflow... or lift a halt'), which signals a control operation, but it collapses the schema's three distinct actions (pause, resume, suspend) into two vague modes and never defines what 'suspend' means or how it differs from 'pause'. It also does not distinguish this tool from siblings like melra_workflow_cancel or melra_workflow_advance.

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?

There is no when-to-use guidance: nothing tells the agent when to choose pause vs suspend vs resume, nor when to prefer this tool over melra_workflow_cancel. The only usage hint is implicit in the word 'halt'.

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