set_temperature

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

No annotations provided, and description is silent on behavioral details like range limits, blocking vs. async, or potential errors. For a mutation tool, more transparency is needed.

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?

Single direct sentence that is front-loaded and efficient. Could include structured hints for parameters, but overall concise.

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?

Without output schema or annotations, description should cover return values and error handling, but it does not. Missing context for a 5-parameter tool.

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 describes all parameters fully (100% coverage). The description adds no extra meaning and omits 'extruder' mentioned in schema, making it less complete.

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 clearly states the action (set temperature) and resource (printer component), with examples (bed, nozzle). It differentiates from sibling tools like set_fan_speed or set_light.

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?

No guidance on when to use this tool or alternatives. No mention of prerequisites or conditions, such as printer state or safety considerations, making it hard to decide.

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