directus_list_flows

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

No annotations are provided, so the description must carry full behavioral disclosure burden. It fails to indicate whether this is a safe read-only operation, what the default pagination behavior is (despite having a 'limit' parameter), or any rate limiting concerns.

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 brief and front-loaded, but the '[UNIFIED]' tag wastes space without adding value. Given the complete lack of schema documentation, the description is actually too concise rather than appropriately sized.

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?

With 4 parameters (including filtering and sorting capabilities), zero schema coverage, and no output schema, the description is insufficient. It omits critical context about query capabilities that would help an agent construct valid filter/sort queries.

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%, and the description completely fails to compensate. No explanation of the required 'site' parameter (what format? which site?), nor the 'filter' syntax, 'sort' fields, or default 'limit' behavior.

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 clear verb ('List') and resource ('automation flows'), and the word 'all' helps distinguish this from sibling 'directus_get_flow' which retrieves a single flow. However, the '[UNIFIED]' prefix is metadata noise that doesn't aid comprehension.

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?

No guidance provided on when to use this versus 'directus_get_flow' or when to apply the filter/sort/limit parameters versus retrieving the full unfiltered list.

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