lights_off

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

No annotations provided, so description carries full burden. Reveals it's a shortcut, mentions auto-acquire and no-op-safe behavior. Does not elaborate on potential side effects, but turning off lights is generally safe. Adequate transparency for a simple toggle.

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?

Three sentences: first states core action and shortcut, second and third provide references. Front-loaded and concise, though references require cross-tool lookup.

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 low complexity (1 param, no output schema, no annotations), description adequately covers purpose, usage, and key behaviors (shortcut, auto-acquire). References to lights_on and set_function fill gaps.

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 has 0% description coverage and only one parameter (address). Description does not add any additional meaning or format guidance for the address parameter beyond the implicit context of locomotive address.

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?

Description clearly specifies the action ('Turn off'), resource ('locomotive headlight'), and explicitly states it's a shortcut for set_function(address, 0, False). Distinguishes from sibling lights_on via reference.

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?

Provides use context by referring to lights_on for F0 explanation and noting same auto-acquire and no-op-safe behavior as set_function. Does not explicitly state when not to use but gives alternative usage paths.

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