set_light

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

With no annotations provided, the description carries full burden for disclosing behavioral traits. It only mentions 'using the printer's MQTT LED command' which hints at the mechanism but does not state if it is a destructive or safe operation, effects on printer state, or required permissions. The tool is a write operation but no side effects are described.

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, front-loaded sentence that efficiently states the action and mechanism. It is appropriately sized for a simple tool, though could be slightly expanded to cover important caveats.

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 lack of output schema and no annotations, the description should explain return behavior or confirmation of action. It does not clarify what happens after setting the light (e.g., success response, visual confirmation). However, the tool's simplicity partially compensates.

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?

Input schema has 100% description coverage, so baseline is 3. The description adds no additional parameter context beyond what the schema already provides (e.g., examples for 'light' node). It does not explain relationships between parameters or typical values.

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 it sets a Bambu printer light node mode using MQTT LED command. This is specific and distinct from other set_* sibling tools like set_temperature or set_airduct_mode.

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 for controlling printer lights but provides no explicit when-to-use or when-not-to-use guidance. It does not differentiate from alternative methods like using the printer's native controls or other tools.

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