node_plugins_clone

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the mutation/safety profile is partially covered by structured data. However, the description adds nothing — it does not say what is copied from the source plugin, whether tags/config are duplicated, or how the new plugin is identified.

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?

Three words, front-loaded, but the brevity is under-specification rather than conciseness — there is nothing here that earns its place because nothing informative is present.

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?

No output schema, no annotation detail beyond the safety hints, and an undocumented required parameter. For a mutation tool an agent must call with a UUID it has to know the meaning of, the description omits everything needed.

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 single required parameter cloneFromUuid has 0% schema description coverage, and the description provides no explanation of it — no indication that it is the UUID of the plugin to duplicate. With only one parameter and no coverage, the description fully fails to compensate.

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?

"Clone Node Plugin" restates the tool name with no added specificity — it says what resource is involved but nothing about scope, resulting object, or how it differs from siblings like node_plugins_create or sub_page_configs_clone. This is effectively a tautology of the name.

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 alternatives (e.g. node_plugins_create for a fresh plugin vs. cloning an existing one), and no prerequisites. The agent gets no basis for choosing this tool over a sibling.

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