reread_ams_rfid

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

With no annotations, the description carries the full behavioral burden. It discloses a key side effect ('can move AMS filament'), a prerequisite (idle and unloaded), and a platform-specific route ('X2D on macOS uses the native official plug-in route'). It omits details like failure behavior or token requirements, but covers the critical safety-relevant traits.

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?

Three short sentences, front-loaded with the core action, followed by a platform note and a safety warning. Every sentence adds distinct value with no audience-irrelevant filler.

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-like operation with no output schema and no annotations, the description supplies purpose, prerequisite conditions, side-effect risk, and platform nuance. It could go further on authentication or expected outcomes, but an agent has enough to invoke it safely.

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 already documents all five parameters including ranges and defaults. The description adds only the implicit scope of 'one AMS slot' and does not elaborate on parameter formats or constraints beyond the schema.

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 states a specific verb ('Trigger') and resource ('Bambu AMS RFID re-read') with explicit scope ('for one AMS slot'). No sibling tool performs a similar re-read action, so it is easily distinguished from the surrounding printer operations.

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?

It gives a clear precondition: 'use only when the printer is idle and unloaded.' This doubles as a when-not rule. No alternative tool is named, but none exists in the sibling list for this exact operation.

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