Fatiar modelo com o Bambu Studio (CLI)

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

With no annotations, the description carries the full burden. It discloses that the tool invokes the Bambu Studio command line, produces a .gcode.3mf file, and implies a non-destructive operation on the input. It does not mention error cases or potential side effects like overwriting existing output files, but the core behavior is clear and not misleading.

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 four concise sentences in Portuguese. It opens with the main purpose, then provides best practices, and finally mentions the next steps. Every sentence adds value with no redundancy or filler.

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?

The tool has 4 parameters (1 required), no output schema, and no annotations. The description explains the tool's purpose, input requirements, and workflow, but does not specify the return format (e.g., whether it returns a success message or file path). While the mention of sending the result implies the output, a clearer statement of the return value would make it complete for an agent.

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 coverage is 100%, so the baseline is 3. The description adds meaningful context beyond the schema by explaining that .3mf project files are preferred and that STL files require a preparatory step in Bambu Studio. This clarifies the input_path parameter's semantics and helps the agent choose valid inputs.

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 (Fatia) and resource (arquivo 3MF), and clearly defines the output (.gcode.3mf). It distinguishes itself from siblings by mentioning the CLU workflow and referring to other tools like bambu_upload_file and bambu_start_print, which clarifies its role in the printing pipeline.

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 explicitly states when this tool is most appropriate (with .3mf projects saved from Bambu Studio containing profiles) and gives a clear prerequisite for STL files (open in Bambu Studio and save as .3mf first). It also suggests follow-up tools, providing concrete usage context.

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