authentik_flows_read

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

Declares 'safe, read-only' but provides no further behavior details (e.g., auth requirements, rate limits, error handling). With no annotations, more detail would be beneficial.

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?

Three sentences with no fluff, proper front-loading of purpose, and example call.

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?

Provides enough for an agent to start, but the generic operation pattern makes it incomplete without listing available operations. The help instruction compensates partially.

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?

Adds meaning to 'operation' by showing help usage and describing parameter passing, but schema coverage is 0% and no operation list is provided. Relies on user knowing help.

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?

Clearly states it queries Authentik auth pipeline config, listing specific resources (flows, stages, policies, sources, events). Distinguishes from write siblings and more general authentik_read.

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?

Implies read-only usage but does not explicitly guide when to choose this tool over siblings like authentik_read or authentik_flows_write. No when-not-to-use advice.

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