get_temperature

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

No annotations are provided, so the description carries the behavioral burden. It clearly signals a read-only operation by using 'Get' and usefully states that both temperature and humidity are returned, adding value beyond the input schema. It does not cover errors or offline behavior, but for a simple read tool 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 a single focused sentence with no filler. It front-loads the action and resource and earns its place without redundancy.

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 simple 2-parameter read tool with no output schema, the description plus complete schema coverage is mostly sufficient. It tells the agent what data to expect (temperature and humidity) and that the target is a specific sensor, though it leaves return formatting and error behavior implicit.

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 description coverage is 100%, so the schema fully documents deviceId and unit, including the F/C enum and default. The description does not add additional parameter-level meaning beyond confirming the reading comes from a specific sensor.

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 uses a specific verb and resource: 'Get temperature and humidity reading from a specific SwitchBot temperature sensor.' It clearly differentiates from sibling get_all_temperatures by scoping to a single sensor.

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 phrase 'specific sensor' implies use when a single sensor's reading is needed, and the sibling get_all_temperatures provides the aggregate alternative. However, it does not explicitly exclude cases such as getting general device status via get_device_status.

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