open_in_slicer

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds meaningful context by noting it launches a GUI app, that it performs no slicing/modification/printing, and that preflight_check should precede it. It doesn't say whether the call blocks, what happens if the file or slicer is missing, or whether the app must already be installed — minor gaps for a GUI-launching tool.

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?

Three short sentences, front-loaded with the action and resource, followed by the scope exclusion and the prerequisite. No filler and nothing buried.

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 2-parameter tool with no output schema, the description covers action, scope, and prerequisite ordering adequately. It omits error behavior (missing file, slicer not installed) and whether anything is returned, but these are secondary for a GUI-open operation.

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 file_path extensions and the slicer_type enum plus its SLICER_TYPE env default are fully documented in the schema. The description adds no parameter-level detail beyond that, which is the expected baseline when the schema does the work.

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 ('Open a model or sliced project in the slicer's GUI') and names the concrete application (Bambu Studio). The negative clause 'Does not slice, modify, or print anything' cleanly separates it from slice_stl and prepare_print_project in the sibling list.

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?

Gives an explicit prerequisite ('Call preflight_check first') and a typical trigger point ('for example after slice_stl'). It lacks an explicit statement of when to avoid the tool beyond the negative clause, but the usage context is clear without inference.

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