awtrix_get_device_state

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds useful behavioral nuance by saying 'current' and 'if available,' signaling that values may change over time and that the active app field can be absent. This 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?

A single, well-structured sentence states the action and the list of returned metrics with no filler. The most important scoping word ('current') appears upfront, and the optionality of the active app is handled compactly.

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?

With no parameters, an output schema present, and annotations covering idempotence/read-only behavior, the description is sufficient for an agent to invoke the tool correctly. It states exactly what hardware metrics will be returned and does not need to cover return formatting because the output schema exists.

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 description has no parameter burden to carry. The baseline for zero-parameter tools is 4, and there is nothing here that reduces the score; the description instead clarifies what the returned metrics are.

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 ('Return') and names the exact resource: current AWTRIX hardware metrics (battery, lux, temperature, active app). It clearly distinguishes this read-only tool from the mutating/action siblings like awtrix_delete_app, awtrix_notify, and awtrix_upsert_app without needing to open the schema.

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 makes it clear this is the status/read tool by saying 'Return current...' while all sibling tools are actions or mutations. It does not explicitly state when not to use it, but the context is clear enough that an agent would select this for reading hardware state rather than for changing anything.

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