ZenML MCP Server

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

No annotations are provided, so the description carries full burden. It states this is a list operation but doesn't disclose behavioral traits like pagination behavior (implied by page/size parameters but not explained), whether it's read-only (safe to assume but not stated), authentication requirements, rate limits, or what happens with empty results. The description merely restates parameter names without explaining their functional impact.

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 brief with a clear purpose statement followed by a parameter list. However, the parameter section is redundant with the schema and doesn't add explanatory value, making it somewhat wasteful. The structure is front-loaded but could be more efficient by omitting the parameter enumeration or replacing it with meaningful guidance.

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 (8 parameters, no annotations, but with an output schema), the description is minimally adequate. The output schema likely covers return values, reducing the need for that in the description. However, for a filtering/list tool with many parameters, the description should explain how filtering works, pagination behavior, and any constraints—none of which are present.

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 0%, so the description must compensate. It lists all 8 parameter names but provides no semantic context beyond what's in the schema titles. For example, it doesn't explain what 'logical_operator' applies to, what format 'created' and 'updated' expect, or how filtering works with multiple parameters. This adds minimal value over the bare schema.

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 ('service connectors in the ZenML workspace'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'list_services' or 'get_service_connector' (singular), which could cause confusion about when to use this specific list tool versus others.

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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'get_service_connector' (singular) and other list tools (e.g., 'list_services'), there's no indication whether this is for comprehensive listing, filtered queries, or specific use cases. The agent must infer usage from the parameter set alone.

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