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

No annotations exist, so the description carries the full behavioral burden. It discloses the shape of the return (name, stage count, tags, default execution settings) and implies a tenant-scoped read, but says nothing about pagination, result limits, ordering, or permissions needed to see another tenant's pipelines.

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?

Three tight sentences with the identity and scope front-loaded, then return shape, then the chaining instruction. No filler, though the enumeration of return fields could be slightly condensed.

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 and no annotations, the description sensibly compensates by naming what is returned and how results feed RunSavedPipeline. For a one-parameter, zero-required list tool this is nearly sufficient; only pagination/limit behavior is unaddressed.

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 single tags filter is fully documented in the schema, including an example value, so the baseline of 3 applies. The description uses "tags" only to describe returned metadata, which mildly risks confusing the filter parameter with a return field, adding no real clarity beyond the schema.

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 saved pipelines") plus a scope qualifier ("for the current tenant"), which separates it from the similarly named ListPipelineTemplates sibling. It doesn't explicitly name or contrast that sibling, so the differentiation is inferential rather than stated.

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?

Gives concrete workflow context: results supply pipeline_definition_h which is then passed to RunSavedPipeline to execute. That tells the agent when this tool sits in a chain, but it never states when to prefer this over ListPipelineTemplates or what conditions would make listing inappropriate.

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