lights_off

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

No annotations provided, but description discloses auto-acquire and no-op-safe behavior, referencing set_function's behavior, which is crucial for agent decision-making.

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: one for core purpose, two for behavioral context and alternatives. No redundancy, efficiently front-loaded.

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?

Covers purpose, alternatives, and behavioral traits, but lacks return value description or error conditions. However, for a command-like tool this is acceptable.

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?

Only parameter is 'address', which is not elaborated beyond schema. Schema has 0% coverage, so description should compensate, but it does not. However, 'address' is a standard concept in this domain, making it moderately clear.

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 it turns off a locomotive's headlight(s) and explicitly contrasts with layout/scenery lighting, differentiating from set_light.

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?

Explicitly tells when to use this (locomotive headlight), when not (layout lighting), and references lights_on for additional context about F0.

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