List saved pipelines

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description does not need to restate safety. It adds value by explaining the exact content of each entry (name, path, one-line summary with task count, site/asset, cadence), and implicitly communicates that this is a non-mutating discovery operation. There is no contradiction between description and annotations.

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 sentences, front-loaded with the core purpose and output details, then a usage hint. No waste, and every sentence contributes meaning. It is appropriately concise for a simple read-only listing tool.

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 zero parameters, a rich output schema (implied), and annotations covering safety, the description fully covers what an agent needs: it specifies what is listed, where from, and why to use it. Nothing crucial is missing.

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 has zero parameters and schema description coverage is 100% (vacuously). The description clarifies that the list is scoped to the trusted pipelines directory (`settings.PIPELINES_DIRECTORY`), which adds meaning beyond the empty schema. Baseline for 0 parameters is 4, and the description meets it.

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 the specific action (list) and resource (pipeline YAML files saved by `save_pipeline`), and details the output fields (name, path, summary). It differentiates from sibling tools like save_pipeline and delete_pipeline by focusing on discovery and referencing the trusted pipelines directory.

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 provides clear context on when to use the tool: before reusing, editing, or deleting a saved pipeline, and cautions against guessing file names. While it does not explicitly name alternative tools or when not to use it, the guidance is actionable and points to the intended workflow.

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