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

The readOnlyHint annotation already establishes this is a safe read, so the description's added value is the field-level disclosure of what comes back (online status, dual-unit temperature, active hold). It stops short of noting behavior when the id is invalid or the thermostat is offline, but the return-shape detail is meaningful context beyond the annotations.

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?

Two compact sentences: the payload summary leads, and the endpoint reference trails as scaffolding. Nothing is redundant or padded.

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?

For a single-parameter read with no output schema, the description usefully previews the returned fields, which is the main information gap an agent would otherwise have. Missing only failure-case behavior (nonexistent id, offline device), which is a modest omission for a simple getter.

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 100% schema coverage and a single required parameter already documented in the schema—including its origin from operto_list_thermostats—the description adds no syntax or format instruction beyond restating 'by id'. Baseline 3 applies when structured data does the heavy lifting.

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 ('Get one thermostat by id') and enumerates what it returns: online status, temperature in Fahrenheit and Celsius, active hold. The endpoint reference confirms the exact API surface, and 'one ... by id' distinguishes it from the sibling list tools.

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 by 'by id' and the schema note that the id comes from operto_list_thermostats, which sketches the list-then-get workflow. However, the description itself names no alternatives or when-not conditions, leaving the agent to infer that operto_list_property_thermostats or operto_list_thermostats is the right path when the id is unknown.

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