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 of behavioral disclosure. It effectively communicates the deprecation status and migration path, which is critical behavioral context. However, it doesn't mention pagination behavior, rate limits, or authentication requirements, leaving some gaps in operational transparency.

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 and appropriately sized. It front-loads the purpose and critical deprecation warning, then provides parameter documentation. Every sentence serves a clear purpose with zero wasted text.

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 (7 parameters, no annotations, but with output schema), the description is complete enough. It covers the purpose, deprecation context, alternative tool, and parameter semantics. With an output schema present, the description appropriately doesn't need to explain return values.

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 7 parameters with brief explanations of their purposes (e.g., 'The field to sort the run templates by', 'The page number to return'), adding meaningful semantics beyond the bare parameter names in the schema. However, it doesn't provide format details (e.g., date format for 'created') or enum values for 'sort_by'.

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 run templates in the ZenML workspace'), making the purpose specific and unambiguous. It also distinguishes this tool from its sibling 'list_snapshots' by explicitly mentioning the deprecated nature of run templates versus snapshots.

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 explicit guidance on when NOT to use this tool (due to deprecation) and names the alternative ('list_snapshots'), including specific usage instructions for the alternative ('list_snapshots(runnable=True)'). This gives clear context for tool selection.

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