Boost fans to maximum

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

Discloses that it runs fans at 100%, is temporary with a default duration, and reverts automatically. No annotations provided, so description carries burden. Could mention what 'reverts' means (e.g., to previous state?), but it's clear enough.

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?

Two sentences with no fluff. First sentence defines action and default, second gives use cases and behavior. Every word earns its place.

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?

Covers purpose, usage, duration, revert behavior. With one optional parameter and no output schema, the description is sufficient for an agent to select and invoke correctly. Minor gap: revert behavior could be more precise.

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 covers parameter fully with description. Description adds context about limited time and default, but does not add new semantic meaning beyond schema. Baseline score 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?

Clearly states it runs all fans at 100% for a limited time, a specific verb-resource-action with distinct behavior. Differentiated from siblings which query status or set auto/specific speeds.

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?

Explicitly mentions ideal use cases (pre-cooling before compile, video export, LLM inference burst). Does not explicitly state when not to use, but context of siblings implies alternatives for granular control.

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