Slice a model with multiple process or override variants and compare the resulting G-code to identify differences.
Slice and compare multiple process/override variants.
| Name | Required | Description | Default |
|---|---|---|---|
| model | Yes | ||
| nozzle | No | ||
| verbose | No | ||
| filament | Yes | ||
| variants | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full behavioral burden. It indicates the tool slices and compares, but does not disclose whether it performs multiple expensive slice operations, what side effects exist, what the output looks like, or any constraints such as model/filament compatibility.
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 short and front-loaded with the core action, and there is no filler text. However, for a tool with 5 parameters, a nested unstructured 'variants' array, and no output schema, this is under-specification rather than appropriate conciseness.
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?
The description is far too thin for the tool's complexity. With no annotations, no output schema, 0% parameter coverage, and a loosely-defined 'variants' array accepting additional properties, an agent cannot reliably determine how to construct inputs or interpret results. Sibling comparison tools are not differentiated.
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 for the 5 parameters, but it only vaguely references 'process/override variants.' It does not explain what each variant object should contain, how 'verbose' behaves, or what 'nozzle' defaults and constraints are beyond the schema's default value.
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 states a specific verb-resource pair: 'Slice and compare multiple process/override variants.' This distinguishes it from single-slice tools like u1_slice, though it does not clarify exactly how it differs from comparison tools like u1_compare_recipes or u1_diff_profiles.
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?
There is no guidance on when to use this tool versus alternatives. The phrase 'compare multiple... variants' implies a multi-variant comparison use case, but no explicit when/when-not conditions or sibling alternatives are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.