List pipelines

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and world scope are covered structurally. The description adds the useful fact that results span two distinct categories (templates plus workspace-saved pipelines), but says nothing about pagination, ordering, or result size. Modest added value against an already-informative annotation set.

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 sentence with no filler, front-loaded with the verb and resource. Every clause carries information, including the cross-reference to the consuming 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?

For a zero-argument, read-only listing tool with no output schema, the description supplies what an agent most needs: what the list contains and which downstream tool uses it. It stops short of describing the returned shape (e.g., identifiers needed to invoke adsoptimiser_run_pipeline), which is the only remaining gap.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4. The description correctly implies the call is unfiltered and returns the full listing.

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 ('List') and a precisely scoped resource ('pipeline templates and the workspace's saved pipelines'), and names the sibling tool (adsoptimiser_run_pipeline) that consumes the result. An agent can distinguish this discovery tool from adsoptimiser_run_pipeline, adsoptimiser_get_pipeline_run, and adsoptimiser_list_jobs without opening any schema.

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 clearly frames the context of use: this is the lookup you perform to find pipelines that adsoptimiser_run_pipeline can start. It does not add explicit exclusions or state when NOT to call it, but the when-to-use signal is unambiguous.

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