list_pipelines

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

With no annotations, the description carries full burden. It mentions pagination and sorting but does not disclose authentication needs, rate limits, safety (read-only), or whether it returns all pipelines or only accessible ones. The behavioral profile is incomplete.

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 concise: two sentences plus an Args block. The main action is front-loaded. No extraneous information. Could be slightly more structured but is efficient.

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?

Missing output schema and description does not explain return format or pagination details (e.g., total count, default page size). Does not differentiate from sibling list tools. Parameter descriptions are basic and omit constraints like valid sort_by fields.

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 coverage is 0%, so description must explain parameters. It provides basic explanations for each parameter (e.g., page is 1-indexed). However, it lacks detail: sort_by does not list valid fields, and sort_order does not clarify case sensitivity or allowed values beyond asc/desc.

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 it lists pipelines with pagination and sorting. The verb 'List' and resource 'pipelines' are specific. However, it does not differentiate from sibling list tools like list_projects or list_workflows, though the resource name is distinct.

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?

No explicit guidance on when to use this tool versus alternatives. The usage is implied by the tool name and description, but no exclusions or comparisons with other list tools are provided.

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