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

Adds real value beyond the annotations: it warns that steps actually fire (texts, emails, webhooks) and recommends user confirmation, which is more concrete than openWorldHint=true alone. It omits whether execution is synchronous, what the response returns, and that repeat calls re-execute (annotations carry idempotentHint=false but the description never reinforces it).

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 tight sentences with the side-effect warning front-loaded right after the action. No filler or redundant restatement of the title.

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?

Covers the most important risk (real outbound side effects, confirm first), which suits a no-output-schema mutation tool. But with three undocumented parameters and no statement of what a call returns or how failures surface, an agent still lacks enough to invoke it confidently.

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% for all three required parameters, so the description is the only source of meaning — and it says only "one existing record." That hints at entityType/entityId but gives no explanation of the workflow `id`, the permitted entity types, or ID formats.

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 a workflow now on one existing record, bypassing its trigger" gives a specific verb (run), resource (workflow), and scope (single existing record, trigger bypassed). It is distinguishable from workflows_manage/workflows_list in practice, but no sibling is named 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?

Implies the manual-execution case by saying it bypasses the trigger, and adds a confirm-with-user caveat. It never states when to prefer workflows_manage or what to do if the record has no matching workflow, so usage is implied rather than spelled out.

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