Alert Rule Edit

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

The description only restates the operation ('Edit an existing alert rule') and adds no behavioral detail beyond annotations. With readOnlyHint=false and destructiveHint=true, an agent can infer mutation, but the description does not explain whether editing replaces the full rule or merges partial fields, or what destructive side effects may occur.

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 no filler. It immediately tells the agent what action is performed and on what resource.

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?

The combination of detailed payload schema and annotations covers most operational context, but the description lacks guidance on update semantics (partial vs. full replacement) and what happens with omitted optional fields. For a mutation tool with destructiveHint=true, this is a meaningful gap despite the rich schema.

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% and the payload parameter is extensively documented with field names, types, and constraints. The tool description itself contributes no additional parameter meaning, so the baseline score of 3 applies.

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 states a specific verb ('Edit'), a resource ('existing alert rule'), and the domain ('LibreNMS'). This clearly distinguishes it from sibling tools like alert_rule_add, alert_rule_delete, and alert_rule_get.

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 word 'existing' implies this tool is for modifying already-created alert rules rather than creating new ones, which provides clear context. It does not explicitly name alternatives or state when not to use it, but the purpose is unambiguous against the sibling set.

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