node_plugins_delete

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the description's "Delete" verb is consistent but adds nothing. It omits whether the deletion is permanent, what happens to nodes still referencing the plugin, or whether any confirmation/force parameter is required for a destructive operation.

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?

At three words the text is short, but this is under-specification rather than conciseness: nothing is front-loaded because nothing beyond the tool name is stated. The brevity leaves the agent with no actionable 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?

This is an irreversible destructive mutation with no output schema and no annotation detail beyond destructiveHint. For such an operation the description should at minimum state impact and irreversibility, and it does neither.

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 0% and the description never mentions the single required uuid parameter. The parameter name is self-explanatory, but the description provides no format, scope, or lookup guidance to compensate for the empty schema descriptions.

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?

"Delete Node Plugin" names a specific verb and resource, so an agent can tell it removes a plugin object rather than a node or user. However, it merely expands the tool name with no differentiation from close siblings like nodes_delete, node_plugins_update, or node_plugins_torrent_truncate.

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, no mention of prerequisites, and no reference to alternatives such as node_plugins_sync or node_plugins_reorder. The agent is given no basis for choosing this tool over the other plugin-mutating siblings.

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