reread_ams_rfid

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

With no annotations, the description discloses key behavioral trait: 'This can move AMS filament'. Warns about idle/unloaded requirement, implying potential risk if used during operation. Could mention more about side effects, but sufficient for safety.

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 efficient sentences: first defines action, second provides critical usage warning. No unnecessary words.

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?

Covers purpose, usage condition, and behavioral side effect. Lacks error handling or return value details, but for a simple triggering tool with no output schema, this is adequate.

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 for all 6 parameters. Description adds no additional information beyond parameter names and defaults already present in 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?

Description states specific verb 'Trigger a Bambu AMS RFID re-read' and target resource 'one AMS slot'. Distinct from sibling tools like 'resolve_3mf_ams_slots' which handles file-based slot resolution, not hardware RFID re-read.

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?

Clearly states precondition: 'use only when the printer is idle and unloaded'. Does not explicitly mention when not to use or list alternative tools, but the condition is critical and well-communicated.

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