authentik_flows_write

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

With no annotations, the description carries full burden. It states the tool is non-destructive, which is a positive disclosure, but it lacks details on idempotency, conflict handling, permissions, or side effects. More behavioral context is needed.

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 concise with four sentences: a clear summary, a usage tip, a general call pattern, and an example. No extraneous information; every sentence serves a purpose.

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?

Given the tool's complexity (multiple sub-operations via open-ended params) and no output schema, the description provides a starting point but is incomplete. The help mechanism is good, but a comprehensive listing or reference would improve completeness.

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 has 0% description coverage. The description adds value by explaining the help operation and giving an example of how to call with operation and params. However, it does not document the structure of params for each operation, which is an open-ended object.

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 clearly specifies the verb (create or update), the resource (Authentik auth pipeline config: flows, stages, policies, sources), and distinguishes it as non-destructive. It also contrasts with sibling tools like authentik_delete.

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 tells how to list available operations via operation='help' and gives an example but does not explicitly guide when to use this tool versus the generic authentik_write or other siblings. The context is implied but not direct.

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