homey_get_sensor_readings

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

With no annotations provided, the description carries the full burden. It transparently indicates a non-destructive read operation ('get') and specifies the exact scope (all sensors across the home). It does not detail return structure or potential limitations, but for a zero-parameter, straightforward 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 sentence with a clear, front-loaded action verb. Every word adds value, and there is no redundancy or filler. It is perfectly concise.

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 zero-parameter tool with no output schema, the description is complete enough to guide selection and invocation. It defines the resource (sensors) and scope (across the home). It could mention what the returned data looks like, but that is not essential for invoking the tool.

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 does not need to explain parameters, and the empty schema fully covers the input contract. No further elaboration is necessary.

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 ('get'), identifies the resource ('current readings from all sensors'), and includes a scope ('across the home'). It clearly distinguishes itself from sibling tools like homey_get_device or homey_get_device_insights by focusing on sensor readings specifically.

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 implies when to use this tool (when current sensor readings from all sensors are needed) but does not explicitly contrast it with alternatives like homey_get_energy_data or homey_get_live_insights. No when-not-to-use guidance is provided, but the scope is clear enough for basic selection.

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