Delete a node plugin shared list by name to remove unused access rules and keep the panel organized.
Delete a node plugin shared list by name
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Shared list name to delete |
Changes observed during successful MCP inspections.
v2.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It conveys destructive intent ('Delete') but does not disclose whether deletion is permanent, cascades to dependent plugin state, fails on nonexistent names, or requires special permissions.
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 sentence that front-loads the action and resource, containing no filler or redundant content.
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?
Adequate for a one-parameter delete operation, but with no annotations and no output schema, the agent is left without information about return values, error behavior, or side effects. It is enough to invoke the tool, but not fully self-contained.
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 only parameter 'name' is already documented as 'Shared list name to delete'. The description's 'by name' mirrors the schema without adding extra format or behavior details.
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'), resource ('node plugin shared list'), and selection criterion ('by name'). It clearly distinguishes from sibling operations like shared_lists_create, shared_lists_update, and shared_lists_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 purpose implies when to use it, but there is no explicit guidance about when to prefer this over alternatives, nor any exclusions or prerequisites. Sibling delete tools are not referenced for routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.