list_pipelines

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

It discloses pagination behavior by instructing the agent to read has_more and total and pass page numbers, which is valuable behavioral context. No annotations are provided, so this detail helps, though it could mention more about authentication or response format.

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?

The description is two succinct sentences, front-loading the core purpose and then adding the pagination detail. Every word earns its place, with no redundancy.

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?

Given the presence of an output schema, return values are covered. The description adds filter and pagination details, making it fairly complete for a list tool. It lacks explicit mention of ordering or potential edge cases, but is adequate for the tool's simplicity.

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 description explains knowledge_cluster_id as an optional filter and hints at the page parameter syntax, but it does not explain page_size or the default page=0, and there's a slight inconsistency with examples using page=1. With 0% schema coverage, the description partially compensates but not fully.

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 clearly states 'List data pipelines' with an optional filter by knowledge cluster, using a specific verb and resource. This distinguishes it from sibling tools like list_sources and list_destinations.

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?

The description implies when to use this tool (when you need to list pipelines) and provides a specific use case with the optional cluster filter. However, it does not explicitly name alternatives or state when not to use it.

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