flow_list_presets

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

With no annotations, the description carries the full burden. "List" implies a read-only, non-mutating operation and it discloses the categories of data returned, which is useful context. However, it says nothing about freshness, whether results are cached or static, pagination, or whether authentication/plan tier affects what is returned — all relevant for a catalog tool.

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?

A single front-loaded sentence with no filler or redundant restatement of the tool name. The only weakness is that the list is compressed to the point of ambiguity — "limits" is undefined and could mean rate limits, quotas, or content limits.

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 zero-param read tool with no output schema and no annotations, the description should explain what the caller actually gets back and in what shape. It names four data categories but not their structure or how they relate, leaving an agent to probe the tool to understand its output. Adequate but with a clear gap.

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?

The tool takes zero parameters, so there is nothing for the description to clarify and the baseline of 4 applies. No conflicting or misleading parameter language is present.

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 ("List") and enumerates the resources returned: format presets, style presets, current models, and limits. An agent can tell this is a discovery/catalog lookup rather than a generation action, distinguishing it from the flow_generate_* and flow_edit_* siblings. It loses a point because the four-item grab bag leaves the shape of the response somewhat fuzzy.

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?

There is no explicit when-to-use guidance, no statement that this should be called before generation tools to discover valid preset names, and no mention of any alternative. The intended use (looking up presets/models before invoking a generator) is only inferable from the tool name and the sibling set, which the description does not reference.

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