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

Annotations already mark the tool as non-read-only and open-world, but the description adds critical operational context: the execution is real, may send real messages, and therefore requires user confirmation. This goes well beyond the annotations without contradicting them.

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?

Four sentences, front-loaded with the action and the most important safety warning. Every sentence earns its place: trigger scope, real-execution warning, follow-up tool, and alternative trigger guidance.

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?

Given the simple one-parameter schema and no output schema, the description supplies the key behavioral context an agent needs: consent, real-world side effects, result retrieval, and trigger-type routing. The only gap is parameter documentation for workflow_id.

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 explain the sole required parameter workflow_id beyond implying it refers to a saved workflow. With a low-coverage schema, the description should compensate but does not provide format, source, or validation details; the parameter name is self-explanatory but insufficiently documented.

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, resource, and scope: running a real test execution of a saved workflow with Manual/Webhook-style triggers. It clearly distinguishes itself from siblings by naming self_heal_workflow for other trigger types and get_execution for reading results.

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?

Explicitly says when to use this tool, when to prefer the sibling self_heal_workflow, and what to do next with get_execution. It also gives a clear consent requirement: ask the user first because it runs for real.

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