set_fermentation_chamber_compressor_delay

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 action and the valid range, which duplicates the schema, and does not disclose side effects, prerequisites, persistence, or response behavior. For a mutation tool, this is a significant gap.

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 sentence that is immediately clear, front-loaded with the action, and contains no fluff or redundant wording.

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 simplicity of the tool (two fully documented parameters, no nested objects, no output schema), the description is largely sufficient. It clearly states the purpose and constraint, though it could benefit from a note about what the response looks like.

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 description coverage is 100%, so the baseline is 3. The description repeats the valid range for minutes but adds no additional meaning beyond the schema, which already describes both parameters.

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 specific action: 'Set the compressor restart delay in minutes for a fermentation chamber.' It uses a verb + resource + attribute, and the name and description distinguish it from sibling tools like set_fermentation_chamber_temperature or set_fermentation_chamber_pid.

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 provides clear context for when to use the tool: whenever you need to set the compressor restart delay. It does not explicitly mention alternatives or exclusions, but the purpose is unambiguous and differentiated from siblings by the specific setting it modifies.

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