gflow_list_models

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

With no annotations, the description carries the burden and does well: 'Static catalog... no browser, no spend' tells the agent this is a cheap, side-effect-free lookup with no external session required. It stops short of stating there are no failure modes or that results are cacheable/stable across calls.

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 clauses: purpose and payload first, then the cost/behavior caveat. No filler, and the identity of the tool is front-loaded.

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?

Complete for a zero-arg catalog tool: an output schema exists, yet the description still previews the relevant fields (label, aliases, reference cap, max duration, aspects, tiers), and it flags the browser/spend characteristics that matter for planning.

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?

Zero parameters, so the baseline is 4; the description correctly omits any argument discussion and instead spends its words on the returned fields.

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+resource ('List the image and video models the generate tools accept') and immediately enumerates what each entry contains, which separates it cleanly from gflow_generate_image/gflow_generate_video and from gflow_list_tools.

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?

Implies the intended context (discovering what the generate tools accept) and rules out browser/spend costs, but never explicitly says 'call this before gflow_generate_image/video to resolve a valid model name,' nor names an alternative catalog tool such as gflow_list_tools.

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