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 covered. The description adds genuinely new information: the meaning of a flow, that a template may have any number of them, and the exact fields returned (flow_id, name, description, length in seconds, steps), which compensates for the missing output schema.

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?

Three short sentences, each carrying distinct payload: definition of the resource, cardinality/shape, return fields, then downstream wiring. Front-loaded with the verb and resource, with zero 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 one-parameter read-only tool with no output schema, the description supplies the domain concept, the return fields, and the cross-tool handoff to create_batch. Nothing an agent needs in order to call it and use its result is missing.

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 100% and the single parameter already documents its origin (search_templates or create_design). The description only restates that the tool operates on a template, adding no syntax or format detail beyond the schema, so the baseline of 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 and resource (list a template's flows) and immediately defines what a flow is, so it is clearly separable from list_pages, get_design, and create_flow. The scope constraint ('a template can have any number') plus the returned field list leaves no ambiguity about what the call produces.

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 names the downstream use: take a flow_id and pass it to create_batch as flowIds to render. It gives no exclusions or comparison against siblings (e.g., when to use get_design or list_pages instead), so it stops short of full when/when-not guidance.

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