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

No annotations are provided, so the description carries the full burden. It usefully discloses the composition of the return set (system vs tenant-specific) and names a key field, but says nothing about permissions required, whether it is strictly read-only, or pagination/result limits for large template libraries.

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 sentences, front-loaded with purpose and scope, then return composition, then the follow-up action. No filler; every sentence adds information an agent can act on.

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, the description compensates by explaining what the list contains and identifying the field to reuse downstream. It is slightly thin on result size, ordering, or pagination for a tenant that may have many templates, but is otherwise sufficient for a zero-param read tool.

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 clarify; the baseline for a parameterless tool is 4. No misleading parameter hints are given.

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) plus a precise resource (pipeline templates) scoped to the current tenant, and clarifies what the result set contains: system templates plus tenant-specific ones. An agent can distinguish this from the sibling ListPipelines (saved pipelines, not templates) from the description alone.

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 clear downstream context — take pipeline_definition_h from the results and POST it to /api/v1/pipelines/templates to clone into a saved pipeline — which tells the agent why and when this tool fits in a workflow. It stops short of explicitly contrasting with ListPipelines or stating exclusions, so it is not a full 5.

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