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

Annotations already establish that this is a safe, read-only, idempotent operation, and the description adds meaningful behavioral context: `quiet_hours` causes sends to wait, `daily_limits` with today’s count causes waits until midnight after the limit, and run history is newest-first with per-step results. It does not describe pagination or general listing behavior, but it is substantially more informative than the annotations 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?

The description is compact and front-loads the main purpose, then packs the mode conditions and behavioral details into as few words as possible. The parenthetical phrasing around `quiet_hours` and `daily_limits` is dense but still readable.

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?

With no output schema, the description does a fair job of explaining the important return modes and some returned fields, including run history ordering. It does not fully describe the top-level list response shape or pagination, but it is adequate for a read-only list tool whose annotations and schema already cover the safety and parameter basics.

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 already 100%, so the baseline is 3. The description still adds meaning beyond the schema by clarifying that `id` retrieves a single definition and that `id` + `runs: true` returns run history ordered newest-first with per-step results. The `limit` parameter is left to the schema, which is acceptable given full 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?

The description clearly states that this is a listing/read tool for workflows and explains the three retrieval modes: all workflows, one definition by `id`, and run history with `id` + `runs: true`. It does not explicitly distinguish itself from siblings such as `workflows_manage` or `workflows_run_now`, which keeps it from a 5.

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?

It gives useful mode-selection guidance (`id` for one definition, `id` + `runs: true` for history), so the usage is more than entirely implied. However, it never says when to choose this tool over `workflows_manage` or `workflows_run_now`, and it provides no exclusions or alternative-tool routing.

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