wp_delete_plugin

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

With no annotations provided, the description carries the full behavioral burden. It discloses two important traits: the plugin will be deactivated first if active, and deletion is permanent file removal. It does not mention permission requirements or failure behavior, but the key destructive consequence is clearly communicated.

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?

Two tight sentences with no wasted words. The main action and resource are front-loaded, the deactivation caveat is parenthetical, and the permanence statement earns its place by clarifying the destructive nature.

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 simple one-parameter tool with no output schema, the description covers the essential context: what gets deleted, that active plugins are deactivated first, and that removal is permanent. Minor omissions such as permissions or return values are not critical for correct invocation.

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 by describing the parameter as 'Plugin file path, slug, or name', so the baseline is 3. The description adds no further clarification about which identifier format is preferred or how plugin resolution works.

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 clearly states the verb 'Delete' and the resource 'WordPress plugin', and it distinguishes itself from the sibling wp_deactivate_plugin by noting that it deactivates first and permanently removes the plugin files. This gives an agent no ambiguity about what the tool does.

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 phrase 'permanently removes the plugin files' implies this tool is for permanent deletion rather than mere deactivation, and the automatic deactivation note provides context. However, it never explicitly names wp_deactivate_plugin as the alternative or states when not to use this tool, leaving the comparison mostly to inference.

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