add_devices_to_group_bulk

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

With no annotations, the description carries the full burden and does so well: it declares the operation non-destructive, preserves existing members, explains the same-VDOM constraint, and warns that requested_count is not a count of changed memberships because FortiManager gives no per-member result.

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 operation, then uses clear Args, Returns, and Example sections. The return-value caveat is not padding; it prevents a likely misinterpretation of requested_count.

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 bulk mutation tool with no annotations, 0% schema parameter descriptions, and an output schema, the description supplies the missing behavioral semantics, parameter meanings, expected return shape, and the relevant alternative tool.

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 documents all four parameters with meaning: ADOM name, target device group name, list of device names, and VDOM with its default of 'root', plus the same-VDOM caveat.

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 opens with a specific verb and resource: adding multiple devices to a device group in one call. It clearly distinguishes this bulk operation from the singular sibling add_device_to_group by explaining the same-VDOM constraint.

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 explicitly states that all devices are added on the same VDOM and directs the caller to add_device_to_group individually for devices needing a different VDOM. That is a concrete when-to-use-this-vs-alternative rule.

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