wordpress_deactivate_plugin

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action (deactivation) without indicating side effects (e.g., loss of settings, impact on site functionality), error conditions (e.g., plugin not found), or permission requirements. The description is insufficient for understanding the tool's full impact.

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 extremely short (one phrase), which is concise but at the expense of essential details. It is not efficiently structured to provide necessary context; it sacrifices substance for brevity.

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 the low schema coverage (0%), missing annotations, and no output schema, the description is critically incomplete. It fails to specify valid plugin identifiers, error handling, or the expected result. The tool's simplicity does not excuse the lack of detail, as the agent still needs guidance 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 description adds no semantic meaning to the single 'plugin' parameter. The input schema has 0% description coverage, and the description does not clarify what format the plugin identifier should take (e.g., slug, file name). This leaves the agent without necessary guidance on how to correctly fill the parameter.

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 'Deactivate a plugin' uses a clear verb and resource, making the tool's purpose immediately understandable. It effectively distinguishes itself from sibling tools like 'wordpress_activate_plugin', though it could be slightly more specific by indicating that the plugin is identified by its slug.

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?

No usage guidelines are provided. The description does not specify when to use this tool (e.g., to disable a plugin temporarily) or when not to (e.g., if the plugin is already deactivated). It also fails to mention any prerequisites, such as the plugin needing to be installed and currently active.

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