Bambu Lab MCP Server

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: it sends a single command, blocks dangerous commands for safety, and implies it's a write operation (sending commands). However, it doesn't cover aspects like error handling, response format, or rate limits, which would be helpful for a tool interacting with hardware.

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 front-loaded with the core purpose in the first clause, followed by an example and safety note. It's only two sentences with zero waste, efficiently conveying essential information without redundancy or fluff.

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 tool's complexity (interacting with a printer, potential safety risks), no annotations, and no output schema, the description is adequate but has gaps. It covers the basic action and safety, but lacks details on return values, error cases, or prerequisites. For a hardware control tool, more context would improve completeness.

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 input schema has 100% description coverage, with the 'gcode' parameter documented as 'G-code command.' The description adds minimal value beyond this by providing an example ('G28' for home), but doesn't elaborate on syntax, constraints, or allowed commands beyond the safety warning. This meets the baseline for high schema coverage.

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 tool's purpose: 'Send a single G-code command to the printer' with an example ('G28' for home). It specifies the action (send) and resource (G-code command), but doesn't explicitly differentiate from siblings like 'printer_set_speed' or 'set_temperature', which might also involve sending commands. This makes it clear but not fully sibling-distinctive.

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 implies usage by mentioning 'Dangerous commands are blocked for safety,' which suggests when to use (for safe G-code commands) and hints at when not to use (for dangerous ones). However, it doesn't explicitly name alternatives (e.g., other printer control tools) or provide clear exclusions, leaving the guidance somewhat implied rather than explicit.

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