Set fan speed

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

With no annotations, the description fully discloses behavioral traits: manual mode, clamping to safe range, TTL expiration, and a failsafe at 102°C. This covers safety and auto-revert behaviors comprehensively.

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 concise and well-structured. The first sentence states the core purpose, followed by parameter explanations, expiration behavior, failsafe, and a typical use case. No redundant sentences.

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 4 parameters, no output schema, and no annotations, the description covers all essential aspects: manual mode setup, parameter meaning, clamping, TTL, failsafe, and typical usage. It is complete enough for an AI agent to select and invoke correctly.

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%, but the description adds meaningful context: the relationship between rpm and percent (percent mapped to min-max range), the mutual exclusivity, and that values are clamped to safe range. It also clarifies that omitting fan applies to all fans.

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 tool's purpose: 'Put the Mac's fans into manual mode at a given speed.' It specifies the resource ('Mac's fans') and the action ('manual mode'), and distinguishes from siblings like boost_fans, get_thermal_status, and set_fan_auto.

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 a typical use case ('raise fans BEFORE starting a heavy build/inference job') and explains the automatic revert after ttl_seconds. However, it does not explicitly state when not to use the tool or compare it to alternatives like boost_fans or set_fan_auto.

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