processDefinition_restartInstancesAsync

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

With no annotations provided, description carries full burden. It successfully discloses the async nature and batch job return value, but omits mutation semantics (what 'restart' entails), failure modes, or monitoring requirements using migration_listBatches.

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 sentences with zero waste. Front-loaded with action and return value, followed by specific usage condition. Every word earns its place.

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?

Adequate for a zero-parameter async operation. Mentions critical batch job return compensating for missing output schema. Could improve by referencing batch monitoring tools, but sufficient for agent selection.

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?

Input schema contains 0 parameters, establishing baseline 4. Description correctly implies no instance-specific filtering is possible via parameters (requires empty property object).

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?

States specific action ('Restart process instances'), scope ('asynchronously'), and key artifact ('returns a batch job'). The 'Async' suffix combined with 'avoid timeout' clearly distinguishes this from the synchronous sibling tool processDefinition_restartInstances.

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?

Provides explicit when-to-use guidance ('when restarting many instances to avoid timeout'), effectively guiding selection over the synchronous alternative. However, it does not explicitly name the sibling tool to avoid.

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