Set fan speed

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

With no annotations, the description carries the behavioral disclosure burden. It does disclose useful behavior: quiet/turbo trigger dedicated modes and intermediate steps are mapped down on 3-speed units. However, it does not describe error behavior, response format, or what happens with the 'auto' value.

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 compact and front-loaded, with the core action in the first sentence and only relevant behavioral caveats afterward. Every sentence earns its place and there is no redundancy with the schema.

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?

For a simple setter this is mostly adequate, but gaps remain: the meaning of 'auto' is unexplained, the relationship to set_quiet_mode and set_turbo_mode is ambiguous, and the lack of an output schema means the agent gets no guidance about responses or errors. It covers the basics but not the full context an agent may need.

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 documents all parameters with 100% coverage, so the baseline is 3. The description adds meaningful semantic detail for the speed enum, clarifying quiet/turbo behavior and how intermediate steps behave on 3-speed units, which goes beyond the schema's bare 'Fan speed level' description.

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 and resource: 'Set the fan speed.' It also adds relevant context about quiet/turbo and 3-speed behavior. However, it does not explicitly distinguish itself from the sibling tools set_quiet_mode and set_turbo_mode, so sibling differentiation is only implied.

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 when-not-to-use guidance is provided. The phrase 'quiet and turbo engage the dedicated modes' hints at special behavior but does not clarify whether set_quiet_mode/set_turbo_mode should be used instead, leaving an ambiguity that the description should resolve.

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