Activate or deactivate a plugin

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

With no annotations, the description carries the full burden. It discloses that changes take effect immediately on the live site and includes a caution to confirm before deactivating. This is significant behavioral context beyond the bare 'change active status'. However, it does not mention potential errors, side effects, or whether activation requires similar confirmation.

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: the first states the action, the second adds a critical warning. It is front-loaded with the primary purpose and contains no redundant information. Every word earns its place.

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 mutation tool with no output schema and no annotations, the description covers the core purpose, immediate impact, and a safety precaution. It does not explain return values or failure modes, but given the low complexity (3 parameters, clear enum), the description is sufficiently complete 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 already provides descriptions for the plugin path, status enum, and site. The description adds no additional semantic detail about how to choose values or what each parameter means beyond the schema. With 67% schema coverage, the baseline is 3, and the description does not elevate it.

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 states 'Change a plugin's active status' which is a specific verb and resource. The title 'Activate or deactivate a plugin' reinforces this. It clearly distinguishes from sibling tools like wp_list_plugins (listing) and wp_create_content (content creation).

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 implies usage for managing plugin state but does not explicitly state when to use this tool over alternatives. The warning to confirm before deactivating provides context but no exclusion or alternative guidance. Usage is implied by the tool's nature as a management action.

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