ZenML MCP Server

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

With no annotations provided, the description carries the full burden. It discloses the default sorting behavior ('sorted by creation date in descending order'), which is valuable context. However, it doesn't mention pagination behavior, rate limits, authentication requirements, or what happens with invalid parameters, leaving gaps for a tool with 5 parameters.

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 well-structured with a clear purpose statement followed by behavioral detail and parameter documentation. It's appropriately sized for a tool with 5 parameters, though the parameter explanations are minimal (single phrases) and could be slightly more informative without losing efficiency.

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's complexity (5 parameters, no annotations, but with an output schema), the description is reasonably complete. It covers the purpose, default behavior, and all parameters. The existence of an output schema means return values don't need explanation, but more behavioral context (e.g., error handling) would enhance completeness.

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 description adds significant value beyond the input schema, which has 0% description coverage. It explicitly documents all 5 parameters (sort_by, page, size, created, updated) with brief explanations, compensating fully for the schema's lack of descriptions. This is essential for understanding what each parameter controls.

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 clearly states the verb 'List' and resource 'pipelines in the ZenML workspace', making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list_pipeline_runs' or 'list_models', which follow similar patterns for different resources.

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 about when to use this tool versus alternatives. While sibling tools exist for listing different resources (e.g., 'list_pipeline_runs', 'list_models'), the description doesn't mention any of them or specify scenarios where this tool is preferred or inappropriate.

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