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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the description isn't obliged to restate it. It does add non-obvious behavioral value by disclosing that each flow is returned with its steps and admins, telling the agent the response is an aggregated/expanded listing rather than a flat list of names. It says nothing about pagination or whether all flows are returned in one call.

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?

A single sentence, front-loaded with the operation and resource, using parentheticals to define the domain term and enumerate the return shape without padding. The trailing 'Elvanto: peopleFlows/getAll' mapping is a compact, useful trace to the underlying API 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?

For a zero-parameter read-only list tool with no output schema, the description covers purpose, domain definition, and return content, and annotations carry the safety profile. The only residual gap is operational detail (pagination, ordering, or result-size limits), which an agent managing large churches might need.

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?

The tool takes zero parameters, so per the rubric the baseline is 4; there is no parameter semantics for the description to add or omit. Nothing in the text conflicts with the empty 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 gives a specific verb (List) and resource (people flows), then defines the domain term with a concrete example ('the church's follow-up pipelines (e.g. First Time Guest Follow Up)'), so an agent unfamiliar with Elvanto terminology still knows what entity this returns. It also distinguishes itself from adjacent siblings like elvanto_list_people_flow_steps and elvanto_list_people_flow_step_people by stating this returns flows with their steps and admins.

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?

Listing is the obviously implied usage, and the mention of steps/admins hints at when this beats the more granular flow-step tools, but the description never states it explicitly or names alternatives. With three closely related people-flow siblings in the toolset, an explicit 'use this to enumerate flows; use X for steps within a flow' would have removed real ambiguity.

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