scan_hue_lights

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

No annotations provided, but description adds transparency about macOS UUID behavior and timeout adjustment. Could explicitly state non-destructive nature, but scan implies no side effects.

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 short paragraphs: purpose, usage guidance, parameter detail. Efficiently front-loads key information with no redundancy.

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?

Fully describes tool's function, prerequisite role, platform nuance, and parameter behavior. Output schema exists, so return values need no further explanation.

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 timeout is explained: purpose (scan time), default (10), and advice (increase if light not found). Adds meaning beyond schema's type/default.

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?

Clearly states the action ('Scan for Philips Hue BLE lights nearby') and the output ('return their names and addresses'). Distinct from sibling tools like get_light_state or set_brightness.

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 instructs to run this first to obtain the Bluetooth address needed for all other tools. Provides platform-specific note and timeout advice.

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