use_ams_filaments

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

No annotations are provided, so the description carries the full burden. It does disclose the ordering semantics and the implicit overwrite of project slots, but it is silent on side effects agents care about: what happens to slots with no loaded tray, whether a connected printer is required, and whether previous slot configuration is destroyed.

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, front-loaded with the primary action, and the second sentence exists solely to disambiguate the optional parameter with a concrete example. Nothing is redundant.

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 one-parameter tool with no output schema and no annotations, the definition covers purpose, default behavior, and parameter mapping. The remaining gap is error/precondition handling (printer must be online, trays empty), which would make it fully self-sufficient.

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 coverage is 0% for the single parameter, but the description fully compensates: it defines the null/default behavior and gives a concrete mapping example ([1, 3] -> project slot 1 = AMS slot 1, project slot 2 = AMS slot 3). That is more than the schema offers.

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?

States a specific verb and resource — set the project's filament slots from the currently loaded AMS trays — and grounds it with a recognizable analogy ('sync AMS'). It does not explicitly distinguish itself from adjacent siblings like sync_with_bambu_studio or set_filament, which keeps it short of a 5.

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 default case ('every loaded tray in order') is spelled out, which implicitly tells the agent when to omit the argument. However, there is no explicit when-to-use/when-not guidance and no comparison to alternatives such as set_filament or ams_load.

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