Delete a New Relic workflow by its ID to remove unwanted workflows. Optionally deletes associated notification channels for full cleanup.
Delete a workflow by ID
| Name | Required | Description | Default |
|---|---|---|---|
| workflow_id | Yes | ID of the workflow to delete | |
| delete_channels | No | Also delete associated notification channels (default: true) |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the burden of behavioral disclosure. It only says 'Delete a workflow by ID' and does not mention that delete_channels defaults to true, potentially deleting associated notification channels, nor does it mention irreversibility or permission needs.
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, focused sentence with no wasted words. It is appropriately terse, though the brevity comes at the cost of missing important behavioral context.
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 operation with no output schema and no annotations, the description is incomplete. It omits the critical cascading behavior of delete_channels and any side-effect warnings, leaving the agent to discover these from the schema alone.
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?
The input schema already provides 100% coverage, including descriptions for workflow_id and delete_channels. The description adds no parameter meaning beyond the tool name, but the schema is self-sufficient, so the baseline 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?
States a specific verb ('Delete') and resource ('workflow') with ID, which clearly identifies the operation and distinguishes it from sibling delete tools targeting other resources (e.g., delete_dashboard, delete_alert_policy).
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?
Provides no guidance on when to use this tool relative to list_workflows or create_workflow, no prerequisites, no warnings about which workflows can be deleted, and no exclusions. The agent must infer the appropriate usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.