turn_on

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

With no annotations provided, the description carries the full burden. It only mentions the action and parameter, omitting behavioral traits such as error handling, permission requirements, or side effects (e.g., does turning on all lights affect all rooms?).

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 concise (two sentences) and front-loaded with the main purpose. However, the 'Args:' formatting adds minor verbosity but is acceptable for a simple tool.

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 single-parameter tool with an output schema, the description covers the basics. However, it lacks details on return values, error states, or behavior when no lights are specified (e.g., all lights vs. nothing), leaving some ambiguity.

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 0%, so the description must compensate. It repeats the schema's 'light_names' parameter as 'Optional list of light names' without adding format, restrictions, or behavior (e.g., case sensitivity, invalid names). Little value beyond the schema.

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 the action ('Turn on') and the resource ('lights'), with an explicit scope ('all or specified'). It effectively distinguishes from siblings like 'turn_off' and 'toggle_lights' by name and verb specificity.

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 usage (turn on all or by name) but provides no explicit guidance on when to use this tool versus alternatives like 'toggle_lights' or 'set_brightness'. No when-not-to-use or cross-references are given.

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