set_print_speed

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 transparency. It discloses the basic action and modes but omits key details: whether the change takes effect immediately, if it requires an active print, and what the default mode is. For a mutation tool, this is insufficient.

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, direct sentence that wastes no words. It is front-loaded with the verb and resource, and the list of modes is concise. Perfectly sized for a simple setter.

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 low complexity (1 required param, simple setter) and missing output schema, the description is minimally adequate. However, it fails to explain context like default mode, impact on ongoing prints, or whether the setting persists. A short note would make it complete.

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 baseline is 3. The description merely reiterates the mode names already present in the schema's enum descriptions, adding no new meaning. It does not clarify how the 'host', 'printer', 'bambu_token', and 'bambu_serial' parameters are used beyond what the schema states.

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 function: 'Set the active print speed mode', and enumerates the four named modes (silent, standard, sport, ludicrous). This specific verb+resource combination distinguishes it from sibling tools like set_temperature or set_fan_speed.

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 provides no guidance on when to use this tool vs. alternatives. It does not specify prerequisites (e.g., printer must be active), nor does it mention when not to use it (e.g., during a critical print phase). The sibling list includes many other setter tools, but no differentiation is offered.

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