list-pipeline-services

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

With no annotations, the description must disclose behaviors but only says 'List', implying read-only. It does not mention pagination, sorting, filtering behavior beyond the schema parameters, or whether deletions affect results. No behavioral traits like auth requirements or rate limits are disclosed.

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 one short sentence with no fluff, efficiently stating the tool's purpose. However, it may be too brief given the complexity of five parameters, but conciseness is about lack of wasted words, which is achieved.

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 tool has 5 parameters, many sibling list tools, and no output schema. The description fails to explain return format, pagination, or filtering behavior. It is severely incomplete for an agent to use effectively without additional context.

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?

Schema description coverage is only 20% (one of five parameters described). The description adds no parameter explanations, so it fails to compensate for the low coverage. The schema's individual parameter descriptions are insufficient, and the tool description does not help.

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 uses a specific verb 'List' and resource 'pipeline services' with an example 'Airflow', which clearly states what the tool does. However, it does not differentiate this list from sibling list tools like list-pipelines or list-database-services, missing a chance to clarify distinct resource types.

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?

No guidance is provided on when to use this tool instead of alternatives (e.g., get-pipeline-service for a single service, or other list tools). The description does not include any exclusion criteria or context for selection.

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