confirm_temperatures

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

With no annotations, the description carries the full behavioral burden and does disclose the key trait: it is read-only and does not itself gate printing, since printing tools enforce their own safety. It also defines the match rule (equality with the file's highest target). It does not say what is returned or what happens when a temperature fails to match, which matters for a verification tool with no output schema.

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 verb and resource, with no filler. The parenthetical enumeration of G-code forms is dense but each item is load-bearing for correct parsing expectations.

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 input semantics and scope well, but with no output schema and no return-value description, an agent cannot know whether a mismatch is reported as a boolean, an error, or a list of differing targets. For a confirmation/verification tool that gap is material.

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 the baseline is 3, but the description adds genuine meaning beyond the schema: it explains that bed_temp/extruder_temp match only when equal to the file's highest target, which is a non-obvious semantic the bare 'Expected highest bed target' wording does not convey. It also clarifies that targets are gathered from multiple G-code dialects, explaining why a single expected value is compared against many reported targets.

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 (report) and resource (every heater target in a G-code file), and enumerates the exact G-code forms covered (S/R, tool-addressed, RepRapFirmware G10/M568, Klipper SET_HEATER_TEMPERATURE). This clearly separates it from siblings like set_printer_temperature (which mutates) and get_printer_status (which reads live state, not a file).

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 a pre-flight verification use case and notes that 'printing tools enforce their own safety gate,' which frames when this check belongs in a workflow. However, it never explicitly says when to use this versus get_printer_status or set_printer_temperature, nor what to do on a mismatch, leaving routing to inference.

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