ZenML MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic action of listing services without mentioning pagination behavior (implied by page/size parameters but not explained), rate limits, authentication requirements, or what the output contains (though an output schema exists). This leaves significant gaps for a tool with 13 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 appropriately front-loaded with the core purpose in the first sentence, but the extensive parameter list (13 items) makes it lengthy. While each parameter explanation is brief, the overall structure could be more concise by grouping related parameters or using a table format.

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 complexity (13 parameters, no annotations) and the presence of an output schema, the description is partially complete. It thoroughly documents parameters but lacks behavioral context (e.g., how filtering works with logical_operator). The output schema reduces the need to explain return values, but more guidance on usage and constraints would improve 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 provides a comprehensive list of all 13 parameters with brief explanations for each (e.g., 'sort_by: The field to sort the services by'), adding substantial meaning beyond the input schema which has 0% description coverage. This fully compensates for the schema's lack of parameter documentation.

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 ('all services in the ZenML workspace'), providing a specific purpose. However, it doesn't distinguish this tool from other list_* siblings like list_models or list_pipelines, which would require mentioning what makes services unique in this context.

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. While the description mentions listing services, it doesn't clarify if this is for monitoring, filtering active services, or other use cases, nor does it reference sibling tools like get_service for single-service retrieval.

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