list-pipeline-services

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

No annotations are provided, so the description must carry behavioral disclosure. However, it only states the basic function without detailing behavior like pagination, filtering limits, or handling of deleted services. The 'include' parameter hints at filtering deleted/non-deleted, but the description does not clarify behavior.

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 very short (one sentence), which is concise but sacrifices crucial detail. It does not use structure like bullet points or sections. While brevity is valued, the lack of parameter info and usage context makes it less effective.

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?

Given the tool has 5 parameters, no output schema, and no annotations, the description is insufficient. It does not specify return structure, pagination behavior, or how the 'limit', 'before', 'after' parameters work. The context from siblings is not leveraged to differentiate.

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 20% (only 'fields' parameter has a description). The tool description adds no explanatory value for the five parameters. For example, 'include' has an enum but no explanation of 'non-deleted', 'deleted', 'all'. The description fails to compensate for the low schema coverage.

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 'List pipeline services (Airflow, etc.)' clearly states the verb 'List' and the resource 'pipeline services', distinguishing it from sibling 'list-pipelines' which lists pipelines, and 'get-pipeline-service' which retrieves a single service. It is specific and unambiguous.

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 versus alternatives like list-pipelines or get-pipeline-service. The description lacks context for appropriate usage, exclusions, or prerequisites, leaving the agent without decision support.

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