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

The annotation supplies readOnlyHint=true, so safety is covered by structured data. The description adds real value beyond it by disclosing what the payload contains ('with their steps and admins'), which matters because there is no output schema to convey the response shape.

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 verb and resource and followed by the disambiguating gloss and example. Every clause earns its place; the 'Elvanto: peopleFlows/getAll' tag is a compact API breadcrumb.

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, the description covers purpose, scope, and a rough sense of the returned data, which is what an agent needs. It stops short of noting pagination, result limits, or ordering, a minor gap given no output schema exists.

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 the schema imposes no semantic burden and the baseline of 4 applies. There is nothing for the description to clarify or compensate for.

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?

States a specific verb (List) and resource (people flows), then disambiguates with a plain-language gloss ('the church's follow-up pipelines') and a concrete example. It also distinguishes itself from the sibling list_people_flow_steps by noting it returns flows 'with their steps and admins' rather than steps alone.

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?

Usage is implied: this is the entry point for enumerating follow-up pipelines, and the example makes the scenario concrete. However, it never states when to prefer this over elvanto_list_people_flow_steps or elvanto_list_people_flow_step_people, and gives no prerequisites or exclusions.

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