turn_off_led

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

The description clearly indicates the behavioral effect (LED turned off) and notes the return value is a status message. With no annotations, this is a transparent description for a simple hardware command, though it does not elaborate on whether it stops active effects like breathing.

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 extremely concise: a short imperative sentence followed by a return value note. Every part is useful and directly relevant, with no filler.

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 no-argument command, the description is nearly complete: it states the action and return type. Some minor context is missing, such as whether this cancels active LED effects from sibling tools, but the output schema likely covers the return details.

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, which earns the baseline score of 4. The description has no parameter information to add because there are no parameters to document.

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 action ('Turn off the LED') with a specific verb and resource. It is immediately distinguishable from siblings like set_led_color and set_led_breathe, which are about setting modes rather than turning off.

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?

Usage is implied by the action: use this when the LED should be off. However, there is no explicit guidance about when to prefer this over sibling tools or any mention of conditions, so the guidance is minimal but not misleading.

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