set_fermentation_chamber_cooling_enabled

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the mutation action without detailing effects, prerequisites, or what happens when toggling cooling while the chamber is in operation. This is a minimal setter description with no extra behavioral context.

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?

The description is a single, front-loaded sentence that states the action and object clearly. Every word earns its place with no fluff or redundancy.

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 the low complexity of the tool and full parameter schema coverage, the description is minimally sufficient. However, it lacks any context about side effects, whether the change is immediate, or how it interacts with other chamber controls. Without annotations, this feels incomplete for a mutation 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?

The input schema already provides complete descriptions for both parameters (chamber_id as UUID, enabled as boolean). The description adds no additional meaning beyond the schema, so the baseline of 3 applies.

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 states the action (enable or disable) and the specific resource (cooling/compressor of a fermentation chamber). It distinguishes this from sibling tools like set_fermentation_chamber_heating_enabled or set_fermentation_chamber_fan_enabled by naming the exact component.

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 explicit when-to-use or alternative guidance is provided, but the specific scope of the tool makes its usage obvious from context. The description implies this is the setter for cooling enablement, not for temperature or other chamber settings.

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