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 states the tool retrieves a pipeline run but doesn't describe what happens if the run doesn't exist (e.g., error handling), whether it's a read-only operation, or any rate limits. This leaves key behavioral traits unspecified for a retrieval tool.

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 sized with two sentences: one stating the purpose and another explaining the parameter. It's front-loaded with the core action, and the 'Args' section adds necessary detail without redundancy. Every sentence earns its place, though minor improvements in clarity are possible.

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 low complexity (1 parameter) and the presence of an output schema (which handles return values), the description is somewhat complete but has gaps. It covers the basic purpose and parameter semantics but lacks usage guidelines and behavioral details, making it adequate but not fully helpful for an AI agent.

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 schema description coverage is 0%, so the description must compensate. It adds meaning by explaining that 'name_id_or_prefix' can be a name, ID, or prefix, which clarifies the parameter's flexibility beyond the schema's string type. However, it doesn't detail format examples (e.g., prefix matching rules) or constraints, leaving some ambiguity.

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 action ('Get') and resource ('a pipeline run'), specifying retrieval by name, ID, or prefix. It distinguishes itself from sibling tools like 'list_pipeline_runs' by focusing on individual retrieval rather than listing. However, it doesn't explicitly contrast with 'get_pipeline_details', leaving some ambiguity.

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. It doesn't mention when to choose it over 'list_pipeline_runs' for multiple runs or 'get_pipeline_details' for pipeline metadata, nor does it specify prerequisites like authentication or existing runs. The description lacks 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.