delete_devices_bulk

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

With no annotations, the description carries the full behavioral burden and does so well: it warns that the operation cannot be undone and explains the asynchronous task semantics ('per-device results only exist once it completes') so requested_count is not mistaken for actual deletions. That is exactly the kind of context annotations would otherwise provide.

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?

Front-loaded and scannable, with a clear warning, Args, Returns, and a minimal example. The first two sentences restate the same idea ('bulk' / 'at once'), which is minor redundancy.

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 destructive, task-backed operation with no annotations and 0% schema coverage, the description covers the essentials: danger warning, parameter meanings, task semantics, and a return-key explanation. It could go further on prerequisites (e.g., ADOM locking or exactly what create_task changes), but the key gap-filling is present.

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 and does: adom, devices, and flags are all explained, including an example flag value ('create_task'). This adds meaning beyond the bare parameter names.

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?

States a specific verb and resource ('Delete multiple devices from FortiManager in bulk') and clarifies it deletes registrations, which separates it from group-membership tools like remove_devices_from_group_bulk. It does not explicitly name the sibling (delete_device) it differs from, so it stops short of a 5.

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 explains what the tool does but gives no when-to-use/when-not-to-use guidance and names no alternative such as delete_device for single-device deletion. The 'in bulk' wording implies the obvious use case, but there is no explicit routing guidance.

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