IDM Temperatursensoren

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds value by listing which specific temperature sensors are included and the unit (°C), going beyond the annotations. It does not mention rate limits or error behavior, but given the strong annotation coverage, this is adequate.

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 succinct and front-loaded with the main purpose. The sensor list is neatly formatted, and the return type is stated. Although it includes bilingual content, each sentence serves a purpose and nothing is extraneous. It is appropriately sized for a simple getter.

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?

This is a zero-parameter, read-only tool with a clear output schema and strong annotations. The description fully covers what data is returned and in what format. No additional context is needed for a competent agent to invoke this tool correctly.

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 has zero parameters, so the baseline is 4. The description correctly notes that it returns a JSON object with all temperatures, which indirectly confirms no input is needed. There is no parameter documentation needed, and the description provides no conflicting information.

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 tool reads all temperature sensors of the IDM heat pump, and enumerates the specific sensors (B33, B34, etc.). This is a specific verb+resource, and it is distinct from sibling getters like hot water status or compressor status.

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 gives clear context by identifying the exact purpose (temperature readings) and the scope (all sensors). It does not explicitly name alternative tools or say when not to use it, but the context from the name and sibling list is sufficient to infer appropriate usage. This is a step above no guidance but lacks explicit exclusions.

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