Pause an ongoing ambient run by providing its run ID. Use this tool to halt an agent-service execution when you need to stop its activity.
Pause an ambient run (agent-service).
| Name | Required | Description | Default |
|---|---|---|---|
| run_id | Yes |
Changes observed during successful MCP inspections.
v1.3.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It only states the action without mentioning side effects, state transitions, reversibility, or prerequisites like whether the run must be 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?
The description is a single concise sentence with no waste. However, it is so terse that it lacks meaningful structure beyond a simple action statement.
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 has one required parameter, no annotations, and no output schema. The description omits essential context such as the run lifecycle, how pause differs from stop, or how to resume. Given its simplicity, this is a significant gap for an agent.
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 meaning to the run_id parameter. It does not explain what run_id refers to, how to obtain it, or any constraints.
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 clearly states the action 'Pause an ambient run' with a specific verb and resource. It distinguishes from siblings like resume/stop by the verb, but does not explicitly contrast them.
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?
No guidance is provided on when to use pause vs. resume, stop, or other run control tools. The description lacks any context about the run lifecycle or selection criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.