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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior context — that the result is typically a single pipeline unless the multiple-pipelines feature is enabled — but says nothing about the shape or size of returned data, and the HTTP path is only marginally informative.

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?

Two compact clauses with the core fact (the pipelines of the account) front-loaded and no filler. The trailing 'GET /pipelines' is the only arguably expendable element, since the annotations already convey that this is a read.

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 simple zero-argument list tool the description covers what is returned at a high level, and the cardinality note is a real aid. However, with no output schema defined, an agent gets no hint about the fields a pipeline object contains (e.g. id, name, steps), leaving a meaningful gap.

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 baseline is 4; there is nothing for the description to disambiguate. No parameter detail is missing or misleading.

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 names the exact resource (sales pipelines of the account) and the parenthetical clarifies cardinality, so an agent knows precisely what it retrieves. It lacks an explicit verb, relying on the title 'List pipelines' to convey retrieval, but the resource is unambiguous and distinct from all siblings (leads, steps, teams, users).

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?

There is no statement of when to call this versus anything else, and no prerequisites or preconditions are given. Because no sibling tool covers pipelines, the risk of misselection is low, but the description offers no positive guidance about context of use.

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