Activate / Deactivate Plugin

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, covering mutation and safety behavior. The description adds operational detail about the plugin basename format, but it does not disclose potential side effects such as plugin activation/deactivation hooks. No contradiction with annotations.

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 two sentences long, front-loaded with the primary action, and includes a concrete example. Every sentence earns its place with no redundancy.

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 tool's simplicity, the schema's thorough parameter descriptions, and the annotations covering safety, the description is complete enough. It provides the critical plugin basename mapping and references the source. It could optionally mention that the plugin must be installed, but this is already implied.

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 covers all three parameters with descriptions, so the baseline is 3. The description adds a cross-reference to wp_list_plugins for the plugin basename, which is useful but does not significantly enhance parameter understanding beyond the schema.

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 ('activate or deactivate') on a specific resource ('an installed plugin') using a specific verb and object. It is distinct from sibling tools like wp_update_plugin or wp_delete_plugin, which handle other plugin operations.

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 description provides clear context for when to use this tool—when you need to toggle a plugin's active status. It also gives a valuable cross-reference to wp_list_plugins for obtaining the correct plugin basename. However, it does not explicitly mention when not to use it (e.g., for installation or updates).

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