tuya_trigger_scene

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

With no annotations, the description must carry the behavioral burden. It only states the action without disclosing side effects (e.g., scene executions may turn devices on/off), authentication requirements, or potential error conditions. No additional behavioral context is provided.

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 of five words, with no redundant information. It is front-loaded and concise.

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?

While the tool is simple and the schema fully documents parameters, the description lacks crucial selection and context information. It does not mention related tools, prerequisites like listing available scenes, or the real-world impact of triggering a scene. For a tool without annotations or output schema, this is insufficient for an agent to confidently use it.

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 input schema already documents both parameters with descriptions (100% coverage). The description adds no extra semantics such as how to discover the scene_id or device_id, or any constraints on values. Baseline of 3 is appropriate.

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 uses the specific verb 'Trigger' with the resource 'Tuya smart scene', clearly stating the action. It distinguishes from general command tools like tuya_send_commands by naming the scene-specific operation, though it doesn't explicitly call out alternatives.

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 usage context is provided. The description does not mention that scene IDs can be obtained via tuya_get_scenes, nor does it indicate when to choose this over tuya_send_commands for controlling devices. This leaves the agent without selection guidance.

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