tuya_set_brightness

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

With no annotations, the description provides one important behavioral constraint: brightness must be between 0 and 1000. However, it does not disclose side effects like whether the light will be turned on if off, or the reversibility of the action, leaving some behavioral ambiguity.

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 concise sentence that front-loads the purpose and includes essential constraints. No redundant information or fluff.

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?

The description covers the key aspects for a simple tool: what it does, how to identify the device, and the valid brightness range. Given the presence of an output schema and the simplicity of the tool, it is mostly complete, though it lacks details on error handling or behavior when the device is unreachable.

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 schema has no parameter descriptions, but the description compensates fully by explaining that device_id can be a name (e.g., 'Living Room Light') and that brightness is an integer with a valid range. This adds significant meaning beyond the raw 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 tool's function: 'Set the brightness of a Tuya light'. It identifies the resource (Tuya light) and the specific action (set brightness), distinguishing it from siblings like set_color_temperature and set_color.

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 gives clear context by specifying that the device can be identified by device_id or name, but it does not explicitly mention when to use this tool versus alternatives like set_color. This is adequate but not explicit about exclusions or alternatives.

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