turn_on

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

No annotations provided, so the description carries the full burden of behavioral disclosure. It says 'turn on' but doesn't describe what happens with the optional brightness parameter (does it default to a previous value or full brightness?), whether targeting 'all' affects undiscovered bulbs, or any state side effects. For a mutation tool with zero annotation coverage, this is a significant gap.

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?

A single efficient sentence with no waste. It's appropriately sized for a simple tool, though it doesn't front-load any usage constraints because it has none.

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 2-param mutation tool with no output schema, the description is minimally adequate but incomplete. It doesn't explain the effect of the optional brightness parameter or clarify behavior when targeting all bulbs, which an agent needs to invoke correctly.

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 description coverage is 100%, so the schema already fully documents both parameters (target with 'all' option, brightness range). The description adds no parameter semantics beyond what the schema provides. Baseline 3 is correct when schema does the heavy lifting.

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?

States a specific verb (turn on) and resource (WiZ bulbs), and the plural 'one or more' distinguishes it slightly from a single-bulb operation. It doesn't explicitly differentiate from sibling turn_off or toggle, but the verb is clear. A 4 is appropriate since the purpose is unambiguous but lacks sibling routing.

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?

No when-to-use guidance, no mention of alternatives like turn_off or toggle. The description says nothing about when this is preferable over toggle, or about prerequisites like discovery. Implied usage only.

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