pause_execution

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

With no annotations, the description must disclose behavioral traits. It only says 'Pause a running program' without explaining side effects, state changes, or whether the program can be resumed. This is insufficient for an agent to understand the tool's impact.

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 sentence that essentially restates the tool name, offering minimal additional structure. While concise, it could be improved with a clearer separation of purpose and parameters.

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?

Given the tool's role in debugging, the description is inadequate. It fails to mention prerequisites (program must be running), effects on threads, or how to resume. No output schema means the description should cover return values, but it does not.

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 50% (only threadId has a description). The tool description does not compensate by explaining the parameters. sessionId is undocumented, and the description does not clarify their purpose or usage patterns.

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 'Pause a running program' clearly indicates the action and resource, and it distinguishes from siblings like continue_execution or step_into. However, it lacks specificity about what 'pausing' entails (e.g., thread-level vs session-level), which could be inferred from the parameters.

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 on when to use this tool vs alternatives. For example, it doesn't mention that this should be used before stepping or that it is required for certain debug actions. The description provides no usage context.

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