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

No annotations are given, so the description carries full burden. It discloses the return fields (id, name, status, etc.) and pagination behavior (nextCursor usage). It also notes to call get_flow for full detail, implying this is a lightweight list. While it doesn't describe side effects (none expected), it gives enough behavioral context for an agent to call correctly. Minor gap: doesn't mention that the list may be filtered by status, but that is implied via the enum.

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 longer than typical but every sentence carries utility: purpose, usage, return fields, examples, pagination advice. It is front-loaded with the primary purpose and uses clear separations. Slightly dense but not verbose. A 4 reflects that it is well-structured and efficient despite its length.

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 list tool with 5 parameters, no output schema, and no annotations, this description is exceptionally complete. It explains return fields, pagination, sorting strategies, and the relationship to sibling tools. There are no missing pieces an agent needs to invoke the tool correctly. The only minor omission is a note on error handling, but that is not expected for a simple read operation.

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. It provides concrete usage for sortBy/sortOrder/limit (e.g., 'For the oldest flow pass sortBy: "createdAt", sortOrder: "asc", limit: 1'), explains cursor for pagination, and advises 'Use limit aggressively'. It does not explicitly explain the status parameter, but the schema's enum (draft, published, all) is self-explanatory and the text mentions 'active/draft work'. Overall, it adds value well beyond the bare 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 states a specific verb ('List') and resource ('the user's automation flows'), and explicitly scopes it to BROWSING many. It distinguishes from siblings by clarifying it is NOT a lookup step and names alternatives (get_flow / search_flows, bulk tool). This is clear and differentiated.

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?

Provides explicit when to use: "Use when the user asks 'what flows do I have?' or wants a recap of active/draft work." Also tells when not to: "NOT a lookup step: for ONE named flow use get_flow / search_flows; to CHANGE several at once use the bulk tool." This is a model example of usage guidance.

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