Delete an ops note in LogicMonitor by supplying the note ID. Use this action to remove a note, with write permission required.
Delete an ops note (requires write permission)
| Name | Required | Description | Default |
|---|---|---|---|
| note_id | Yes | Ops note ID to delete |
Changes observed during successful MCP inspections.
v4.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveHint=true and readOnlyHint=falsecars. The description adds the write-permission requirement, which is useful operational context beyond the annotations. It does not explain idempotency outcomes, but the annotations cover that hint.
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. The permission note is tucked parenthetically and adds value without bloating the description.
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 simple, single-parameter delete operation, the description plus annotations are sufficient. It could mention behavior for nonexistent notes or confirm response format, but idempotentHint and destructiveHint cover the key expectations.
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%: the note_id parameter is described as 'Ops note ID to delete'. The description adds no further parameter guidance, but none is needed given the schema's clarity.
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 an ops note'. This clearly distinguishes it from sibling tools like add_ops_note, update_ops_note, and get_ops_note, which are all present in the sibling list.
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 intended use is implied: use this when you need to delete an ops note. However, it does not explicitly compare against alternatives like update_ops_note or get_ops_note, nor does it state when deletion would be inappropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.