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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description doesn't need to re-establish safety. It does add real behavioral context: Flows are workspace-shared (visibility scope), the call is Free, and returned header names, prompt text and sheet values are customer data rather than instructions (a prompt-injection warning). It omits any return shape or pagination/volume behavior, so with annotations carrying the safety profile a 3 fits.

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?

Four short sentences, front-loaded with the resource definition and followed by routing, cost and data-trust notes; nothing is redundant. The 'Free.' fragment and the injection warning are slightly jarring in placement but each carries information.

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 simple, read-only, single-optional-parameter listing tool with no output schema, the description covers what the resource is, who sees it, cost, and how to drill into one Flow. The only meaningful gap is that it never mentions archived Flows despite exposing an include_archived flag.

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 100% and the single include_archived parameter is fully documented in the schema, so the baseline is 3. The description adds no meaning about archived Flows or why one would include them, so it neither compensates nor detracts.

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?

Description immediately defines the resource as the workspace's saved multi-step pipelines built from scrape, verify, AI and gate steps over a Google Sheet, which is specific and concrete. It doesn't state the listing verb explicitly (that comes from the name/title) and doesn't distinguish itself from sibling list_* tools, so it stops short of 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 explicitly routes single-Flow inspection to get_flow ('get_flow shows one Flow's spec, inputs and outputs'), giving a clear use-it-here vs use-it-there boundary. It says nothing about when to prefer other list_* siblings or when a Flow listing is unnecessary, so no explicit exclusions.

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