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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: run history is newest-first and includes per-step results explaining skips and failures. It stops short of describing pagination or limits, but adds meaningful return-context.

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, both dense with useful routing information, with the base list behavior front-loaded before the conditional modes. 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?

For a read-only list tool with full schema coverage and no output schema, this description covers the primary modes, ordering, and content of results well. Minor gap: it never mentions the `limit`/pagination behavior, which the agent must infer from the schema.

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 100% schema coverage the baseline is 3, but the description goes further by explaining the interaction between `id` and `runs: true` and the ordering/content of run output, which the schema only states tersely ('With id: return run history instead'). It does not mention the `limit` parameter, leaving that entirely to the schema.

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 opens with a specific verb and resource ('List workflows') and enumerates the returned fields (trigger, step count, active state, last run). It clearly distinguishes the three usage modes (all workflows, one full definition, run history) so an agent can identify the tool unambiguously among siblings like workflows_create/delete/run_now.

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 explicit conditional instructions: pass `id` for a single workflow's definition and `id` plus `runs: true` for run history. It does not state when *not* to use it or name alternatives, but the mode-selection guidance is clear and actionable.

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