Rote List Pipelines

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

The description offers significant behavioral context beyond the annotations and schema. It explains that it reads the registry file on each call (implying real-time updates) and explicitly defines error handling—an empty registry results in an empty list, not an error.

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 highly efficient, grouping all essential information (what it lists, how often it refreshes, error handling) into a cohesive and logically structured paragraph without any padding.

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?

The definition is complete; it clearly dictates what the tool does, how it interacts with the system (registry read), and how it behaves under non-ideal conditions (empty registry), making agent invocation straightforward.

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?

Given that the schema description coverage is 100%, the baseline is 3. The description does not elaborate on the meaning of the 'runtime' enum values or how they interact with the output list.

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 provides a precise definition of the action (List) and the resource (compiled pipelines), detailing exactly what information is returned (name, runtime, trigger points, etc.). It immediately establishes its function and scope.

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?

While it doesn't explicitly say 'do X instead of Y', it defines the scope of the data source (the server's registry) and its real-time nature, which implicitly guides when this tool is necessary (e.g., for current, live pipeline status).

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