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

Annotations already convey readOnly=false and idempotent=true; the description adds the key behavioral fact that resuming creates a new durable workflow job rather than continuing the old one in place. It does not explain side effects on the original job, but that is partially covered by destructiveHint=false.

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?

A single sentence that front-loads the action and adds the key qualification; no filler or repetition of schema information.

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?

For a two-parameter workflow-control tool this is mostly adequate, but it leaves open what the call returns, how the new job is tracked, and what 'needs-review' means operationally. Since there is no output schema, these gaps matter for an agent deciding whether the call succeeded.

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 does not mention workflowJobId or idempotencyKey. workflowJobId is inferable from the tool name, but idempotencyKey gets no semantic explanation, and the description fails to compensate for the lack of parameter documentation.

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 names a specific action ('Resume'), a specific resource ('platform-managed research workflow'), and the condition ('stopped or needs-review'), and adds that it runs as a new durable job. This clearly distinguishes it from sibling start/cancel/status tools even without schema inspection.

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?

It explicitly states the intended scope: workflows that are stopped or need review. The 'Resume' verb and sibling names make the contrast with start/cancel/status evident, though it does not name an alternative tool outright.

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