get_printer_filaments

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

Without annotations, the description provides good behavioral context: it retrieves live data over MQTT, specifies output components (slot summary, resolved paths, confidence, recommendations), and implies a read-only operation. No side effects or permissions are mentioned, but the core behavior is clear.

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?

A single, information-dense sentence conveys the tool's purpose, method, and key outputs without extraneous words, achieving high conciseness.

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 no output schema, the description lists the main return components and operating conditions, providing sufficient context for an agent to understand what the tool returns and when it is applicable. Could be slightly more explicit about the output structure.

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 100%, so baseline is 3. The description adds value by explaining that bambu_model and nozzle_diameter are used to resolve filament profiles and that the printer model condition triggers recommendations, going beyond the schema's parameter descriptions.

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 identifies the verb 'Get' and the resource 'live AMS/external filament inventory from the printer over MQTT', distinguishing it from any sibling tools that focus on printer status, slot resolution, or other 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?

The description implies that the tool is for live inventory retrieval and mentions a condition (when printer model is known) for recommended load_filaments, but lacks explicit guidance on when to use this tool versus alternatives like resolve_3mf_ams_slots or get_printer_status.

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