wordpress_delete_plugin

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It mentions the deactivation prerequisite, which is helpful, but it says nothing about permanence, file removal, error conditions, or required permissions. For a destructive operation, this is insufficient.

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 sentence is concise and front-loaded, avoiding unnecessary verbosity. However, it is so brief that it omits essential details about the parameter format, though the structure itself is clean and direct.

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?

Given this is a mutation tool with no annotations and no output schema, the description should compensate by explaining the parameter format, side effects, and success criteria. It only covers the action and one prerequisite, leaving significant gaps for an agent to use it correctly.

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 schema has one 'plugin' parameter with no description (0% coverage). The description merely repeats 'plugin' without clarifying whether it expects a slug, plugin file path, or display name. This is a critical gap that the description fails to address.

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 action ('Delete a plugin') with a specific resource, distinguishing it from sibling tools like activate_plugin or deactivate_plugin. The additional precondition ('must be deactivated first') further clarifies the tool's purpose.

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?

Provides a clear usage condition: the plugin must be deactivated first. This implies the correct workflow (deactivate before deleting) but does not explicitly mention when to use this versus alternatives like deactivate_plugin or get_plugin_status. Still, it offers useful context beyond a bare description.

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