OrcaSlicer MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It describes what the tool checks (binary reachability, directory accessibility) but doesn't disclose critical behavioral traits: what permissions are required, whether it performs active tests or passive checks, what happens if checks fail (errors vs. warnings), or what the output format will be. For a diagnostic tool with zero annotation coverage, this leaves significant gaps.

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 a single, efficient sentence that front-loads the core purpose ('diagnose the server environment') followed by specific checks. Every word earns its place with no 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?

Given the tool's diagnostic nature, no annotations, and no output schema, the description is incomplete. It doesn't explain what the output will contain (e.g., status codes, detailed error messages, structured results), how to interpret results, or what actions might follow from the diagnosis. For a tool that presumably returns important system information, this is inadequate.

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 tool has zero parameters with 100% schema description coverage, so the schema already fully documents the absence of parameters. The description appropriately doesn't discuss parameters, which is correct for a parameterless tool. Baseline for zero parameters is 4, as there's nothing to compensate for.

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 with specific verbs ('diagnose', 'check') and resources ('server environment', 'OrcaSlicer binary', 'settings/work directories'). It distinguishes from siblings by focusing on system health rather than slicing operations or profile management. However, it doesn't explicitly differentiate from all siblings (e.g., 'search_settings' might overlap conceptually).

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?

The description implies usage context ('diagnose the server environment') suggesting this tool should be used for system troubleshooting. However, it provides no explicit guidance on when to use this versus alternatives, no prerequisites, and no comparison to sibling tools like 'search_settings' which might also reveal accessibility issues.

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