set_ams_drying

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

With no annotations, the description carries the full burden of behavioral disclosure for a state-changing operation. It never says what a start/stop does to an in-progress print, whether it requires the printer to be idle, whether it is reversible, or what errors occur on unsupported platforms, so the mutation is largely opaque.

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?

Two sentences, purpose front-loaded, no filler. The second sentence is dense and jargon-heavy ('native official plug-in route') but is a genuine constraint rather than padding.

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?

For a mutation tool with no annotations and no output schema, the description covers the platform-routing caveat but omits preconditions, side effects, and failure modes. The agent has enough to pick the tool but not enough to predict its behavior.

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 every parameter (host, action, ams_id, bambu_token, bambu_serial) is already documented in the schema. The description restates the ams_id 128 AMS-HT case that the schema already covers, adding no new syntax or constraint information.

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 first sentence gives a specific verb+resource pair ('Start or stop the AMS filament drying cycle') that no sibling tool covers, so the agent can identify it immediately. It is not, however, explicitly differentiated from nearby siblings like get_printer_filaments or reread_ams_rfid.

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?

Usage is implied by the action enum and the platform note ('X2D on macOS, or Linux with the native helper installed...'), which hints at a conditional routing requirement, but there is no explicit when-to-use, when-not-to-use, or named alternative.

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