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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is structured. The description adds value beyond them by stating that no messages are sent and no proposed changes are applied, plus the free/no-credits behavior — useful operational context an agent cannot get from the hints alone.

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 non-effect guarantee front-loaded and the cost note as a short trailing clause. No filler.

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 input schema has a two-branch anyOf (operation=workflow with automationId+definition, versus operation=source with node+timeZone), and the description says nothing about these modes or what a preview returns (no output schema). It is adequate at the top level but incomplete for a polymorphic preview tool.

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?

With 75% schema description coverage, the schema already documents accountIds, userStatement and idempotencyKey. The description adds nothing about the required 'input' union (the 'workflow' vs 'source' operations), which is the highest-value parameter information here. Baseline 3 applies.

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 (preview) and resource (automation or integration source) and clarifies the effect (no messages delivered, no changes applied). It never names a sibling such as workflows_list, so the differentiation is only implicit.

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?

'Without delivering messages or applying its proposed changes' implies the pre-commit use case, but there is no explicit when-to-use rule or named alternative (e.g. 'use workflows_list to enumerate, use this before applying'). The routing signal is inferable rather than stated.

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