Temperature Sensor

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

Annotations already declare readOnlyHint and idempotentHint; the description adds context about what data is included and excludes. No contradictions with annotations. The description usefully clarifies scope beyond 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 sentences, no waste. First sentence defines purpose and output fields; second sentence provides usage exclusions and parameter hint. Highly efficient.

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?

Given tool complexity (8 parameters, 1 required, output schema), the description covers everything needed: what it does, when to use, parameter guidance, and exclusion of overlapping cases. Output schema exists, so return values need not be elaborated.

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%, so parameters are well-documented. The description adds specific guidance for the unitId parameter (suggesting victron_discover). This extra context elevates from baseline 3.

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 retrieves temperature sensor data from com.victronenergy.temperature and lists specific fields (temperature, type, humidity, pressure, status). It distinguishes from siblings by noting that battery temperatures from inverters/chargers are handled by other tools (victron_vebus_status, victron_solar_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?

Explicitly states when to use (dedicated temperature sensor inputs) and when not to use (battery temperatures from inverters/chargers, directing to alternatives). Provides guidance on finding unitId via victron_discover.

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