set_airflow_horizontal

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

Description lacks behavioral disclosure such as whether the operation is reversible, requires special permissions, or has side effects. With no annotations to rely on, the tool definition is insufficient in transparency.

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, clear sentence that immediately states the tool's function. It is concise with no wasted words.

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?

The description fails to provide complete context for the operation. It does not explain the meaning of the position values (e.g., 'left-lc-right' represents vane orientation), nor does it describe the expected outcome or any prerequisites. Given no output schema and no annotations, more is needed for completeness.

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% and the description does not add additional parameter semantics beyond the enum values and default IP. Baseline score of 3 is appropriate as the schema already documents parameters adequately.

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 specifies the verb 'Set' and the resource 'horizontal vane/airflow position', and distinguishes from sibling 'set_airflow_vertical' by mentioning horizontal.

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 guidance on when to use this tool versus alternatives like set_airflow_vertical or set_swing_mode. The description only states the function without context.

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