directus_create_flow

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. Beyond the implied mutation in 'Create', it reveals nothing about idempotency, side effects, return values, or required permissions for flow creation.

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 (one sentence), but the '[UNIFIED]' tag wastes valuable leading space without aiding agent comprehension. The core message is front-loaded but contaminated with metadata noise.

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 complex infrastructure tool creating automation workflows with 8 parameters and no output schema, the description is grossly inadequate. Critical concepts like flow status, icon defaults, and the relationship between flows and operations are undocumented.

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% (8 parameters, none documented in schema). The description completely fails to compensate, providing no guidance on the 'trigger' format, 'site' identifier conventions, or the structure of 'options' and 'accountability' parameters.

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 the basic action ('Create') and resource ('automation flow'), but the '[UNIFIED]' prefix is noise that adds no semantic value. It fails to distinguish from sibling tool 'directus_create_operation' (which creates steps within flows), leaving ambiguity about the tool's scope.

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 no guidance on when to use this versus 'directus_update_flow' or 'directus_trigger_flow'. No prerequisites are mentioned (e.g., valid trigger types, site configuration), and no exclusions or alternatives are listed.

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