services_set_climate_mode

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

With no annotations, the description must disclose behavioral traits, but it only states the basic action. It omits details about return values, error conditions, side effects (e.g., turning on/off the unit), or entity availability requirements. The existence of an output schema is not leveraged.

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 immediately conveys the action and the parameter values. It is free of superfluous words and follows a clear verb-resource structure.

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 (2 required string parameters, output schema exists), the description is minimally adequate but lacks details like error handling, device compatibility, or that entity_id must refer to a climate entity. It meets basic needs but leaves gaps for an AI agent.

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 has 0% description coverage, but the description adds meaning by listing the allowed values for hvac_mode (heat, cool, auto, off, fan_only, dry). However, it does not clarify what entity_id should be (e.g., a climate entity) or that the values may not be supported by all devices.

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 verb 'Set' and the resource 'climate HVAC mode', and lists the possible mode values (heat, cool, auto, off, fan_only, dry). It distinguishes itself from sibling tools like services_set_light_color or services_set_cover_position by specifying the domain.

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 no guidance on when to use this tool versus alternatives, such as checking if the entity is a climate device or considering other climate-related services. It does not mention prerequisites or complementary actions.

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