Bambu Lab MCP Server

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention if this is a destructive operation, requires specific printer states, has side effects, or involves rate limits. For a tool that likely interacts with hardware, this is a significant gap in transparency.

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 directly states the tool's purpose without unnecessary words. It's front-loaded and appropriately sized for a simple tool, with zero waste or redundancy.

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 no annotations, no output schema, and a tool that likely performs a hardware operation (filament change), the description is incomplete. It lacks details on success/failure conditions, error handling, or what the tool returns. For a potentially complex action, more context is needed to ensure safe and effective use.

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 fully documents both parameters ('tray' and 'target_temp'). The description only mentions the tray parameter range (0-3), adding minimal value beyond the schema. It doesn't explain the relationship between parameters or provide usage context, so baseline 3 is appropriate.

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 action ('Change to') and resource ('AMS filament tray'), specifying the tray range (0-3). It distinguishes from sibling tools like 'ams_unload_filament' by focusing on switching trays rather than unloading, though it doesn't explicitly contrast them. The purpose is specific but could be more detailed about what 'change' entails.

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?

No guidance is provided on when to use this tool versus alternatives like 'ams_unload_filament' or other printer control tools. The description implies usage for filament switching but lacks context on prerequisites, timing, or exclusions. It's a basic statement without operational context.

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