Get current heating status of a home

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

Annotations already establish readOnly, idempotent, non-destructive, and the description correctly does not contradict them. It adds useful payload visibility (boiler state, unreachable devices, low batteries, open windows), but says nothing about freshness/latency, single-home defaulting, or error behavior for unreachable devices — which is what an agent most needs here.

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?

A single tight sentence with no filler, and the most salient content (current temperature/setpoint/mode) comes first. The structure is a noun phrase rather than a verb-led statement, which slightly weakens front-loading of intent.

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?

Output schema exists, so re-listing return fields is redundant rather than harmful, and the parameter is fully documented by the schema. What is missing is the ambiguous-case handling: when to pick this over the heating summary, room status, or room comparison siblings, and whether it covers one home or all homes.

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?

With one parameter at 100% schema description coverage, the schema already explains home_id and even points at netatmo_list_homes and the single-home default. The description adds nothing about the parameter, so baseline 3 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?

The description enumerates what the tool reports (per-room temperature/setpoint/mode/demand, boiler on/off, alerts), which makes the resource scope clear even though it omits an explicit verb. It does not distinguish itself from close siblings such as netatmo_get_room_status, netatmo_get_heating_status, or netatmo_get_heating_summary, so an agent cannot route on the text 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?

There is no when-to-use guidance and no mention of alternatives, despite four deployed siblings that return overlapping room/heating data. The only implicit cue is the word 'every room', which hints at whole-home scope but is never stated as a selection rule.

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