pause_execution

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 doesn't state what state the execution transitions to, whether the pause is immediate or queued, whether it's resumable, any side effects, or whether permissions are required. The single sentence provides no behavioral context beyond the verb itself.

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 short (6 words), which shows restraint but crosses into under-specification. It's front-loaded but lacks any additional value-adding sentences about behavior, alternatives, or effects. Minimalism here isn't quite the same as disciplined conciseness.

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?

This is a mutating tool (pauses execution) with no annotations and no output schema, so the description must compensate. There are 2 parameters with 100% schema coverage, but the description fails to disclose the state transition, reversibility, prerequisites, or interaction with resume_execution. For a lifecycle-affecting tool, this is inadequate.

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 100%, so both parameters (executionId and reason) are documented in the schema. The description doesn't add meaning beyond the schema, but per the rubric, baseline is 3 when coverage is high. The reason parameter's optionality and semantics are only implied by the schema, not elaborated.

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 workflow execution' uses a clear verb (Pause) and resource (workflow execution), identifying the core action. However, it doesn't distinguish itself from siblings like resume_execution, start_workflow, or manage_execution, nor does it clarify any scoping nuances (e.g., does it pause one execution or all in a workflow instance). It's minimally clear but lacks distinguishing context from closely related tools.

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 guidance on when to use this tool versus alternatives like resume_execution or manage_execution. No conditions, prerequisites, or context are provided for when pausing is appropriate or what state the execution must be in. The description offers no exclusions or alternative tool references.

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