list_lights

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

With no annotations provided, the description must carry the behavioral burden. The verb 'List' and the phrase 'current state' make it clear this is a read-only inspection operation and not a mutating action. It does not mention authentication or rate limits, but for a zero-parameter read operation the core behavior is transparent.

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 a single sentence that front-loads the action and resource, then specifies the relevant returned state fields. Every word earns its place, and there is no redundant 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 simple, zero-parameter, read-only list tool with no output schema, the description adequately states what it does and what the response includes. It could additionally mention response format or authentication expectations, but these are minor gaps given the low complexity and the presence of a separate hue_auth sibling.

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 no parameters, and the schema is an empty properties object, so there is no parameter documentation burden. The description adds value by explaining what the returned data will contain, which is relevant context despite the lack of parameters.

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 states a specific verb ('List'), a clear resource ('all Philips Hue lights'), and the meaningful content of the result (on/off, brightness, color). It is readily distinguishable from sibling tools like set_light and set_all_lights because it is read-oriented rather than write-oriented.

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 implies this should be used when an agent needs the current state of lights, but it does not explicitly state when to avoid it or mention alternatives. Sibling names like set_light and set_scene make the contrast inferable, but the description itself provides no direct routing guidance.

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