devicegroup_add

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

Annotations indicate destructiveHint=true (mutation) and readOnlyHint=false, consistent with the description. However, the description adds no further behavioral context (e.g., permissions, side effects). Annotations carry the behavioral burden; description is minimal.

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 a single sentence, concise and to the point. It could include more context without being verbose, but is not overly terse.

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 existence of an output schema and the tool's relative simplicity (one parameter), the description provides adequate context for a creation operation. It does not mention prerequisites or error cases, but the schema covers payload structure.

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 100% with detailed payload description including examples. The description adds no extra meaning beyond 'Add a new device group'; it does not elaborate on parameter relationships or constraints beyond the schema.

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 'Add a new device group to LibreNMS', with a specific verb ('Add') and resource ('device group'). This distinguishes it from sibling tools like devicegroup_update or devicegroup_delete.

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 implies usage context (adding a new group) but provides no guidance on when to use this tool vs. alternatives like devicegroup_add_devices or when static vs. dynamic types apply. The schema includes type distinctions but no usage direction.

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