wordpress_activate_plugin

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Activate a plugin' without detailing whether it requires specific permissions, changes the database, or what happens if the plugin is already active. This is insufficient for an action-oriented tool.

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 a single sentence, which is concise but overly minimal. It is front-loaded, but it does not earn its place by providing enough information. Adding a bit more context (e.g., input format) would improve without sacrificing conciseness.

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 simple tool but lack of output schema and annotations, the description is incomplete. It does not address what happens when the plugin is already active, or if the plugin slug is invalid. For a tool that modifies state, more context on behavior is expected.

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 has 0% description coverage, and the description does not explain the 'plugin' parameter. It fails to indicate whether it expects a slug, a file name, or a full path. This leaves the agent guessing about the correct input format.

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 a plugin' with a specific verb and resource. It distinguishes itself from the sibling 'wordpress_deactivate_plugin' by indicating activation vs deactivation. However, it does not specify what 'plugin' means exactly (e.g., slug or file name), which could cause ambiguity.

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 guidance is provided on when to use this tool compared to alternatives like 'wordpress_plugin_exists' to check if a plugin exists before activation, or 'wordpress_get_plugins' to list available plugins. There is no discussion of prerequisites, side effects, or scenarios where activation is appropriate.

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