node_plugin_delete_shared_list

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

No annotations are provided, so the description carries the full burden. It does not disclose that this is a destructive irreversible operation, whether it requires specific permissions, or what happens to dependent configurations. The presence of a 'confirm' parameter hints at a confirmation gate, but the description never explains this behavior.

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 very short, which is good for front-loading, but it relies on a raw HTTP method and URL path rather than a natural-language explanation. The tag line adds little value, and the structure feels like auto-generated boilerplate rather than purposeful communication.

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 endpoint with no annotations, no output schema, and a nested required body parameter, the description is insufficient. It does not cover side effects, confirmation requirements, error conditions, or the meaning of the name parameter's pattern. An agent would need to read the schema closely and still lack behavioral context.

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 50%. The description mentions deleting 'by name' but does not explain the nested body object, the name pattern or length constraints, or the purpose of the confirm flag. The confirm parameter is documented in the schema itself, so the description adds nothing 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 states a specific verb (DELETE) and resource (Shared List by name), and the URL path narrows the scope to node plugin shared lists. It does not explicitly distinguish itself from siblings like node_plugin_delete_config or node_plugin_update_shared_list, but the resource is clear enough that an agent can identify the operation.

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?

There is no when-to-use guidance beyond the tag 'Node Plugins Controller'. The description does not mention alternatives such as node_plugin_update_shared_list or node_plugin_sync_shared_list, nor does it state prerequisites or when deletion is appropriate.

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