wordpress_activate_plugin

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

With no annotations, the description carries full responsibility for behavioral disclosure. 'Activate a plugin' implies a state change but does not mention side effects, required permissions, error conditions, or return behavior. This is minimal disclosure for a mutation operation.

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 only three words, which is too underspecified to count as efficient conciseness. It omits essential usage and parameter details, making it closer to an unhelpful stub than a concise description.

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?

The tool is simple, but with no output schema and no annotations, the description must be more complete. It offers no information about prerequisites, side effects, or the tool's role among many plugin-related siblings, leaving the agent without enough context 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 schema has one required string parameter 'plugin' with no description, and schema description coverage is 0%. The tool description adds nothing about what format the plugin identifier should take (slug, path, name), leaving the parameter ambiguous and failing to compensate for the schema gap.

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 uses the verb 'Activate' with the resource 'plugin', clearly stating the action and resource. It is not a tautology and is distinguishable from sibling tools like wordpress_deactivate_plugin or wordpress_delete_plugin, though it lacks any detail about the plugin's identity or activation scope.

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 context is provided. The description does not state when to use this tool versus alternatives like wordpress_get_plugin_status, wordpress_plugin_exists, or wordpress_deactivate_plugin, nor does it mention prerequisites such as the plugin being installed or the user having permissions.

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