Devicegroup Delete

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

The annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds only the fact that lookup is by name, and says nothing about what is destroyed alongside the group (membership mappings, alert bindings) or whether the group must already exist.

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?

A single front-loaded sentence with the verb, resource, source system, and key all up front. No waste, though it is terse enough that there was room for one clarifying clause about side effects.

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?

With one required parameter, full schema coverage, an output schema, and annotations carrying the destructive/idempotent semantics, the minimum an agent needs to invoke it is present. The gaps are around consequences of the deletion, which a destructive tool would ideally disclose.

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 100%, so the sole parameter is documented by the schema itself, giving a baseline of 3. The description ('by name') actually narrows the schema, which accepts 'name or ID to delete', introducing a slight ambiguity rather than adding meaning.

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 (Delete) and resource (device group) scoped to LibreNMS, with the lookup key (by name) made explicit. It cleanly separates this from sibling destructive tools like device_delete or location_delete because the resource is named. It stops short of explicitly routing the agent away from adjacent devicegroup_* siblings.

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?

No when-to-use guidance, no prerequisites, and no exclusions relative to siblings such as devicegroup_remove_devices or devicegroup_update. The agent gets no signal about whether the group must be empty, what happens to member devices, or when to prefer another tool.

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