slice

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

With no annotations, the description carries the full burden; it does add real value by disclosing the outputs (G-code path, metrics, warnings, placements, config check). However it omits key behaviors for a potentially long-running, file-writing operation: whether it writes to disk, whether it overwrites existing files, expected duration, and what failure looks like.

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?

Two compact sentences with the action front-loaded and the return payload enumerated second. No filler, though the return list is packed rather than prioritized.

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?

With no output schema and no annotations, the description does cover return values, which is its main job here. But it leaves gaps around the lone parameter's behavior, write semantics, and prerequisites, so an agent could invoke it without knowing whether it will clobber files or fail on a missing plate setup.

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 single parameter output_path has null default and 0% schema coverage, and the description never mentions it. It is unclear whether omitting it means no file is written, a default path is used, or an existing file is overwritten — a meaningful gap given the tool writes G-code.

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?

States a specific verb and resource ('Slice the bed') and enumerates what the operation produces (G-code path, metrics, warnings, placements, config check). It clearly reads as the slicing action, distinct from read-only siblings like get_gcode_metrics or analyze_toolpaths, though it never names a sibling to route against.

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 slice versus when to inspect existing results, and no prerequisites are stated (e.g. models loaded on plate, profiles selected). An agent must infer all preconditions from context.

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