Get Netatmo home details

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description contributes the genuinely useful caveat that results are topology only (not live values), which prevents misuse; it says nothing about auth requirements or error behavior, but with annotations present that gap is minor.

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 sentence with the scope front-loaded and the disambiguating caveat in parentheses. Nothing is padded or repeated from structured fields.

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 and annotations covering safety, the description only needs to frame scope, and it does so well. The one gap is that listing 'schedules' alongside a netatmo_get_schedules sibling leaves it unclear whether schedule definitions or merely schedule references are returned.

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 schema text already explains that home_id comes from netatmo_list_homes and is optional for single-home accounts. The description says 'one home' but adds no format, fallback, or resolution detail beyond what the schema provides, so the 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?

States a specific verb and resource ('Details of one home') and enumerates the payload scope: heating mode, schedules, rooms, devices. It explicitly distinguishes itself from the status family, so an agent can separate it from netatmo_get_home_status or netatmo_list_rooms without opening a schema.

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 parenthetical 'use the status tools for live values' gives an explicit when-not-to-use rule and points at an alternative tool family. It stops short of naming the exact sibling (netatmo_get_home_status) and doesn't clarify the overlap with netatmo_get_schedules, which it also claims to cover.

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