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

Annotations already carry destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuinely useful context beyond that: publishing and communication steps still enforce their own approvals, telling the agent that some workflow steps may not execute unconditionally. This is consistent with the annotations, not contradictory.

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 and roughly 20 words, with the core action and scope front-loaded and a single valuable caveat following. Every sentence earns its place; there is no fluff or redundancy.

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?

The description covers the core action and one behavioral nuance, which is adequate for a simple run command. However, for a destructive, open-world tool with an undocumented nested input parameter and no output schema, it leaves real gaps: what shape the input should take and what the call returns are both unaddressed.

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%, so the description bears the full burden of explaining parameters. It only implies that workflowId identifies the saved workflow; the `input` object — its structure, purpose, and how it maps to workflow inputs — is entirely unexplained. This is a meaningful gap for an agent preparing a call.

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?

"Run one saved workflow belonging to the authenticated tenant" states a specific verb (Run), a specific resource (saved workflow), and a scope constraint (authenticated tenant). This naturally distinguishes it from siblings like create_workflow_agent and run_localtry_command by resource type, though it does not name those alternatives explicitly.

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?

No when-to-use or when-not-to-use guidance is provided, and no sibling is named as an alternative. The tenant scoping offers mild context, but the description never tells an agent how to choose between this tool and run_localtry_command or create_workflow_agent. The approval sentence is a behavioral note, not usage-routing guidance.

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