assign_sdwan_template_bulk

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

No annotations are provided, so the description bears the full burden. It only states the action and basic parameters, but fails to disclose behavioral traits such as whether the assignment overwrites existing configurations, if it is synchronous or asynchronous, whether the ADOM must be locked, or error handling. This is insufficient for a mutation tool.

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 brief summary followed by parameter explanations. It avoids unnecessary words. However, it could be slightly more structured (e.g., using bullet points) for readability, but overall it is efficient.

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 tool's complexity (writes to multiple devices) and lack of annotations, the description is incomplete. It does not cover prerequisites (e.g., adom lock), side effects (e.g., overwriting existing assignments), error scenarios, or execution outcomes beyond a vague 'Assignment result.' The output schema exists but does not compensate for missing behavioral context.

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 coverage is 0%, but the description adds meaningful parameter semantics: 'adom: ADOM name', 'template: SD-WAN template name', and 'devices: List of devices [{"name": "dev1", "vdom": "root"}, ...]' – clarifying the expected structure of devices. This compensates for the lack of schema descriptions.

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 'Assign an SD-WAN template to multiple devices,' specifying the verb (assign), resource (SD-WAN template), and scope (multiple devices). It distinguishes from sibling tools like assign_sdwan_template (single device) and assign_system_template_bulk (system template).

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 does not provide guidance on when to use this tool versus alternatives like assign_sdwan_template (single device) or assign_system_template_bulk. It lacks explicit when-to-use, when-not-to-use, or prerequisite information.

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