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 mentions that deployments include 'status, URL, and metadata' and 'tie back to snapshots,' adding some context. However, it doesn't disclose critical behavioral traits like whether this is a read-only operation, authentication requirements, error handling, or rate limits, which are essential for a tool with no annotation coverage.

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 starts with a clear purpose statement, provides context about deployments, and lists parameters with brief explanations. Every sentence adds value, and there's no redundant or 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 (3 parameters, no annotations, but with an output schema), the description is fairly complete. It explains the purpose, parameters, and context of deployments. The output schema likely covers return values, so the description doesn't need to detail them. However, it lacks behavioral transparency and usage guidelines, which slightly reduces 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?

Schema description coverage is 0%, so the description must compensate. It provides clear semantics for all three parameters: 'name_id_or_prefix' as the identifier, 'project' as an optional scope with default behavior, and 'hydrate' for additional details. This adds significant value beyond the bare schema, though it could be more detailed (e.g., format examples).

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 tool's purpose: 'Get detailed information about a specific deployment.' It specifies the verb ('get') and resource ('deployment'), and explains what deployments represent. However, it doesn't explicitly differentiate from sibling tools like 'list_deployments' or 'get_deployment_logs', which would be needed for 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 explicit guidance on when to use this tool versus alternatives is provided. The description doesn't mention sibling tools like 'list_deployments' for listing multiple deployments or 'get_deployment_logs' for logs, nor does it specify prerequisites or exclusions. Usage is implied but not clearly articulated.

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