OrcaSlicer 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 mentions 'slice a model file' (implying a processing action) and a timeout parameter, but lacks details on permissions, side effects (e.g., file creation/deletion), error handling, or output format (G-code specifics). This is insufficient for a tool with potential file system impacts.

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 concise and front-loaded, consisting of a single sentence that directly states the tool's purpose and key parameters. Every word contributes to understanding without redundancy or unnecessary elaboration.

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?

For a tool with no annotations and no output schema, the description is incomplete. It doesn't explain the output (G-code file details), error conditions, or behavioral traits like whether it modifies input files or requires specific environment setups. Given the complexity of slicing operations, more context is needed.

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 100%, so the schema fully documents all parameters. The description adds minimal value by summarizing parameters ('input/output filenames and optionally profiles'), but doesn't provide additional context like file format constraints or profile interactions beyond what's in the schema.

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: 'Run OrcaSlicer CLI to slice a model file.' It specifies the verb ('slice') and resource ('model file'), though it doesn't explicitly differentiate from sibling tools like 'analyze_gcode_metadata' or 'list_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?

No guidance is provided on when to use this tool versus alternatives. The description mentions optional profiles but doesn't specify prerequisites, dependencies, or scenarios where other tools might be more appropriate, such as using 'get_profile_content' for profile details first.

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