Bambu Lab MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Start printing') but does not describe what happens during printing, error conditions, permissions needed, or how it interacts with other printer operations (e.g., pausing with 'printer_pause'). This leaves significant gaps in understanding the tool's behavior beyond the basic 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?

The description is a single, efficient sentence that front-loads the core action and prerequisite, with zero wasted words. It directly communicates the purpose and usage context without unnecessary elaboration, making it highly concise and well-structured for quick comprehension.

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?

Given the complexity of a printing tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects like error handling, state changes, or what the tool returns, which are critical for an AI agent to use it correctly. The description covers the basic action but fails to provide a complete operational context.

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 schema already documents all parameters thoroughly. The description does not add any additional meaning or context about the parameters beyond what the schema provides, such as explaining the implications of 'bed_type' choices or 'timelapse' effects. This meets the baseline for high schema coverage but does not enhance parameter understanding.

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 clearly states the specific action ('Start printing') and resource ('a file already on the printer SD card'), and distinguishes it from the sibling tool 'ftp_upload_file' by noting the file must be pre-uploaded via that tool. This provides precise differentiation and avoids confusion with file upload operations.

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 to use this tool: after a file has been uploaded via 'ftp_upload_file'. However, it does not mention when not to use it or alternatives for printing from other sources, which limits full guidance. The context is clear but lacks exclusions or comparisons to other printing-related tools like 'printer_send_gcode'.

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