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

Annotations already declare readOnlyHint, idempotentHint, and no destructive behavior, so the description adds no new safety-related trait. It does add useful context about ordered stages and the canonical_locked flag, but does not disclose further behavior such as filtering, pagination, or permissions.

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 a single front-loaded sentence stating the action and resource immediately, with a second sentence adding a useful data detail. There is no filler, repetition, or wasted text.

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 simple read-only list with one optional parameter and no output schema, the description covers what is listed and key return semantics (ordered stages and canonical_locked flag). It does not mention pagination or whether inactive or archived templates are included, but these are minor for this straightforward list.

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 only parameter, request_id, is optional and undocumented, and schema description coverage is 0%. The description does not mention it, but because request_id is generic and self-explanatory, this is not a major usability gap. Still, the description adds no parameter-level meaning.

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 names a specific verb ('List'), a specific resource ('the organization's pipeline templates'), and elaborates that ordered stages and the canonical_locked flag are included. This clearly distinguishes it from sibling read/create/update pipeline tools and other *_list tools.

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 scope ('organization's pipeline templates') and list verb make the intended use clear against single-item read and mutation siblings. It does not explicitly name exclusions or tell the agent to prefer yardstick_pipelines_read for a single pipeline, so it falls just short of full routing guidance.

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