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 needs no restating. The description adds that results are paged and gives the underlying endpoint, but says nothing about ordering, default result volume, or how pagination terminates beyond what the schema's next_page note implies.

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 front-loaded sentence: what is listed, what fields come back, and that it is paged. The trailing 'GET /pipelines' is mildly redundant but harmless. No wasted sentences.

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?

With no output schema, the field enumeration usefully covers the return shape, and the schema fully covers parameters. The gap is selection context: nothing here tells the agent when this unfiltered pipeline listing should be chosen over the candidate-scoped, job-scoped, or filtered pipeline siblings.

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?

Schema description coverage is 100%: both page and per_page have bounds, defaults, and usage guidance ('Pass the previous reply's next_page'). The description only echoes 'paged', which adds no semantics beyond the schema, so the baseline 3 applies.

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 and resource ('List candidate-to-job pipelines') and enumerates the returned fields (candidate id, job id, rating, workflow id, status id), so the agent knows exactly what data comes back. It does not distinguish this from the several sibling listers (cats_list_candidate_pipelines, cats_list_job_pipelines, cats_filter_pipelines), which keeps it below a 5.

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 when-to-use guidance and no named alternative. With four sibling pipeline tools in scope, the agent has to infer from the name alone whether this is the unfiltered, cross-candidate/cross-job listing or something narrower.

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