add_device_to_group

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the operation is non-destructive and describes the return status/message keys, but it does not mention permission requirements, idempotency, behavior when the device is already in the group, or error conditions.

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 front-loaded with the core action and then uses compact Args/Returns/Example sections. The structure is easy to scan, and the example adds practical clarity without excessive verbosity.

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-device add operation, the description covers parameters, the non-destructive behavior, return keys, and an example. An output schema exists, so return details need not be exhaustive, but missing permission/error context keeps it from being fully 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?

Schema description coverage is 0%, so the description must compensate. It labels all four parameters and states the vdom default of 'root', but it does not clarify constraints, expected formats, or ADOM/device/group naming rules.

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 states a specific verb and resource: 'Add a single device to a device group.' The word 'single' distinguishes it from the sibling bulk tool add_devices_to_group_bulk, so an agent can select it without opening the schema.

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?

It gives clear context for adding one device and notes that existing group members are preserved, making the non-destructive nature explicit. It does not explicitly name alternatives such as add_devices_to_group_bulk or remove_device_from_group, so there is no full when/when-not routing guidance.

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