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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: no indication that this is a read-only listing, no mention of pagination, result volume, or ordering. The only behavioral hint is 'with status', which is too vague to act on.

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?

It is a single short sentence with no wasted words, but it errs toward under-specification rather than conciseness. Nothing is front-loaded because there is essentially only one fragment of content.

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 listing tool with no annotations and no output schema, the description should at minimum say what a pipeline record contains or how results are shaped. Combined with a crowded sibling set of list_* tools, the definition leaves an agent without enough to decide or interpret the call.

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 there is nothing for the description to disambiguate; the baseline for a 0-param tool applies. No parameter-related gaps exist.

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 phrase 'The account's pipelines with status' names the resource (pipelines) and the scope (the account), but it is a noun phrase with no verb, and 'with status' is ambiguous — it is unclear whether statuses are returned, filtered, or required. It does not distinguish this tool from siblings like list_veilles or list_modules beyond the noun.

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 guidance at all on when to call this instead of list_veilles, list_modules, or get_pipeline_schema. The description gives no prerequisites, no filtering conditions, and no exclusions.

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