ZenML MCP Server

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It mentions filtering/sorting parameters but doesn't explain pagination behavior, rate limits, authentication requirements, or what happens with invalid inputs. For an 11-parameter tool with no annotation coverage, this is insufficient disclosure.

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 front-loaded with the core purpose but then devotes most space to a parameter list that duplicates schema information without adding meaningful context. The parameter section feels like wasted space rather than helpful elaboration, reducing overall 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 (11 parameters, filtering capabilities) and absence of annotations, the description is minimally adequate but incomplete. While an output schema exists (reducing need to describe returns), the description lacks crucial context about filtering logic, pagination, and error conditions that would help an agent use it correctly.

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 lists all 11 parameters with brief labels, but with 0% schema description coverage, it doesn't adequately compensate. While it names parameters like 'logical_operator' and 'stage', it doesn't explain their purpose, valid values, or how they interact. The parameter list adds some value but falls short of fully documenting semantics.

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 model versions for a model'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'get_model_version' or 'list_models', which would require explicit comparison to achieve a perfect score.

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 'get_model_version' (for a single version) or 'list_models' (for models rather than versions). The description only states what the tool does, not when it's appropriate.

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