Somneo Raumklima

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine behavioral context beyond that: a concrete data-quality caveat that the humidity reading diverged ~15 percentage points from a Shelly H&T in the same room and should not be used unchecked as a room value — valuable, hard-to-infer information.

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 sensor list is front-loaded and the caveat is clearly marked with a warning glyph. The phrase describing current value plus device average is slightly dense, but every sentence carries information and nothing is filler.

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?

With an output schema present, return format need not be spelled out, and the no-parameter, read-only nature is fully covered by annotations. The description supplies the one thing structured fields cannot: the trustworthiness caveat on the humidity reading, making it essentially complete for this simple tool.

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 tool takes zero parameters, so the baseline is 4. The description correctly adds nothing parameter-related, and there is no schema surface for it to compensate for.

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?

Names the specific resource (Somneo room sensors in the bedroom) and enumerates the exact measurements returned (temperature, humidity, lux, dB) plus their scope (current value and device average). An agent can distinguish this read-only climate tool from the somneo_wecker_* alarm-clock siblings by name and content alone.

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?

Usage is implied rather than stated: it is clear this is the tool to call for room climate readings, and it cautions against trusting the humidity value unchecked. However, it never explicitly says when to use it versus any alternative (e.g. an external Shelly source) nor states any prerequisite.

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