set_property

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

No annotations are provided, and the description does not disclose important behavioral traits such as side effects, authentication requirements, rate limits, or error handling for invalid property names or values. As a mutation tool, critical behaviors are omitted.

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, with a clear purpose statement followed by a structured Args section. Every sentence adds value, though the Args format could be slightly more compact. Overall, it is efficient and front-loaded.

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?

Given the lack of output schema and annotations, the description does not explain return values (e.g., success/failure) or prerequisites (e.g., device online, auth). For a mutation tool with three parameters and no structured guidance, the description is insufficiently complete.

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 provides only types (string) with no descriptions (0% coverage). The description compensates effectively by explaining each parameter: did as device ID, prop_name with examples like 'power', 'brightness', 'temperature', and value with common types and example values ('on'/'off', 0-100).

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 it sets device property values to control devices, with concrete examples like '开灯、调亮度、设温度' (turn on light, adjust brightness, set temperature). It distinguishes from sibling tools such as get_property (read) and list_devices (list).

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 provides examples of when to use the tool (controlling devices by setting properties) but does not explicitly state when not to use it or mention alternatives for similar tasks like run_action or run_scene. The usage context is implied but not clearly delineated.

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