slice_model_file

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

With no annotations, the description must carry the behavioral burden. It discloses the confirm=true guard, the output format, and the auto-discovery fallback for profiles, which is useful. However, it does not describe side effects such as files written, potential failure modes, or what happens when required profiles are missing.

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 compact and front-loaded: the primary purpose and the critical confirm requirement appear first, followed by the profile scenarios. Every sentence adds information, though the second paragraph is a bit dense.

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 six parameters, no output schema, and no annotations, the description covers prerequisites but omits parameter meanings, return/result behavior, and failure handling. It gives the agent enough to attempt a simple case but not enough to use all options confidently.

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 should compensate, but it only meaningfully explains confirm=true and the source-format implications. plate, orient, output, and arrange are left entirely to the agent's inference from their names.

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 names a specific action ('Slice'), the accepted input formats ('STL/3MF'), and the concrete output ('.gcode.3mf'), so an agent can tell exactly what the tool does. It is clearly distinct from the printer_* sibling tools, which concern printer control rather than slicing.

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?

It distinguishes two usage scenarios: STL/STEP inputs require machine/process/filament JSON, while a project .3mf with embedded settings does not, and it flags that confirm=true is mandatory. It does not explicitly state when not to use the tool, but the situation-dependent guidance is concrete and actionable.

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