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

With no annotations, the description carries the full burden of behavioral disclosure. It does communicate that the operation is read-only ('Browse', 'Returns names + descriptions') and what the result will contain. However, it does not disclose pagination behavior, default limits, or how category filtering behaves, which are relevant because of the limit/cursor/category parameters.

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?

The description is two sentences with no filler. The core purpose and examples are front-loaded, followed by usage trigger, output summary, and next-step routing. Every sentence earns its place.

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 browse/list tool with zero required parameters and no output schema, the description conveys the essential purpose and output contents. Gaps remain around pagination, the meaning of category filtering, and the effect of limit/cursor. The next-step pointer to duplicate_flow is helpful, but the completeness is only adequate, not rich.

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 0%, so the description must compensate for the three undocumented parameters. It provides example categories (welcome messages, lead generation, customer support) which loosely map to the category parameter, but it never explains limit, cursor, or category semantics. The parameter names are self-explanatory, but the description adds no explicit value on top of 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 uses a specific verb ('Browse') and a clear resource ('pre-built system flow templates'), with concrete examples like welcome messages and lead generation. It is clearly distinguishable from sister tools like list_flows and generate_flow, and it establishes a bridge to duplicate_flow for next steps.

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?

The description explicitly says 'Use when the user says...' and provides two example utterances, making the triggering context clear. It also mentions cloning via the templates UI or duplicate_flow once selected, giving a path forward, though it does not explicitly say when not to use this tool in favor of list_flows or search_flows.

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