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

The description adds useful behavioral context beyond the annotations: call/artifact access avoids a new charge, cancel prevents new dispatch, and resume requires eligibility and current authorization. It does not contradict the destructiveHint or idempotentHint annotations, though it leaves some operational details to the annotations and schema.

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 dense sentence that front-loads the main operations and contains little wasted text. The phrasing is somewhat packed, but each clause corresponds to a distinct supported action.

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 seven-parameter tool with an output schema and full schema description coverage, the description is complete enough to understand the action surface and key caveats. It could be stronger if it explicitly related this multi-action tool to the singular workflow_run sibling.

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 100%, but the description adds meaning to the action parameter by mapping enum values to concrete behaviors like paging stored provider-call responses or artifacts and resuming eligible runs. It does not elaborate on parameter formats, but the schema already documents those thoroughly.

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 states specific verbs and resources for each supported action: list runs, get status, page provider-call responses or artifacts, cancel dispatch, and resume runs. It clearly identifies the tool as a multi-action workflow-run controller, though it does not explicitly distinguish itself from the sibling workflow_run or workflow_definition 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?

It gives contextual cues for several actions, such as paging stored provider-call responses or artifacts 'without a new charge' and resuming only an 'eligible run with current authorization.' It does not provide explicit when-not-to-use guidance or name alternative sibling tools for overlapping cases.

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