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

Annotations already flag destructiveHint=true, idempotentHint=false and openWorldHint=true, and the description adds real value by saying it overrides the schedule and returns per-step results. It does not, however, warn what the destructive side effects are (e.g. posts actually being published or credits spent), which is exactly the context annotations can't convey.

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, no filler; the core behavior is front-loaded and the usage note follows. Every clause contributes 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?

It correctly notes that step results are reported, which compensates for the absent output schema. But for a destructive, non-idempotent execution tool with a near-identical sibling (start_workflow), the description should clarify side effects and disambiguation, and it does neither.

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%, so the single 'id' parameter, including the id-or-name flexibility, is already fully documented in the schema. The description adds nothing beyond it, which matches the baseline for complete schema coverage.

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 a specific verb and resource ('Runs a workflow immediately') plus scope ('whatever its schedule says'), which is concrete and actionable. However, it does not differentiate from the sibling 'start_workflow', leaving the agent to guess which one to pick.

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?

'Use it to show the user what their workflow actually produces before leaving it to run on its own' gives one implied context. It offers no when-not guidance and never mentions start_workflow or stop_workflow, so the boundary between the run-family siblings is left to inference.

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