print_3mf

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

With no annotations, the description carries the full burden. It helpfully discloses the auto-slice fallback when gcode is missing and warns that a wrong bambu_model can damage the printer, which is real behavioral context. But it omits whether the call blocks until print completion, failure/rollback behavior, and auth prerequisite details for an irreversible physical action.

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, then the auto-slice behavior, then the safety constraint in caps. Nothing is wasted, though the 'IMPORTANT' warning largely duplicates the schema's own 'REQUIRED' wording rather than adding new information.

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 33-parameter, no-annotation, no-output-schema tool that physically drives hardware, the description is minimally adequate: it names the action and the one hard requirement. It says nothing about connection-mode selection, slicer prerequisites, or the irreversible nature of a print job, which an agent would need to make a confident call.

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 33 parameters are already well documented in the schema, including enums for bed_type, slicer_type, connection_mode, and others. The description adds only the emphasis that bambu_model is required and dangerous to get wrong, which the schema itself already states, so it does not meaningfully exceed the baseline.

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 states a specific verb and resource ('Print a 3MF file on a Bambu Lab printer') and discloses the auto-slice behavior, so the core action is unambiguous. However, it does not distinguish itself from near-identical siblings such as print_3mf_bambu_network or start_print, leaving the agent to infer which variant to pick.

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 use this tool versus the many overlapping print siblings (start_print, start_print_job, print_3mf_bambu_network, x2d_native_control). The only routing-adjacent guidance is the internal note that bambu_model must be supplied, which is a prerequisite rather than a use-when rule.

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