wordpress_get_active_plugins

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

No annotations are provided, so the description carries the full burden. 'Get' implies a read-only operation, but the description does not explicitly state that it has no side effects, nor does it mention any details about the returned plugin data (e.g., version, status). It is minimally transparent but not misleading.

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, five-word sentence that is entirely front-loaded and contains no wasted words. It directly states the operation and the scope.

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 tool with no parameters, no annotations, and no output schema, the description is sufficient. It clearly indicates the action and the data returned (all currently active plugins). Nothing more is needed for this simple read operation.

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 tool has zero parameters, and the input schema is empty. Per guidelines, a tool with 0 parameters receives a baseline of 4. The description adds no parameter information because there is nothing to add.

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 a specific verb ('Get') and a clear resource ('all currently active plugins'), explicitly limiting scope to active plugins. This distinguishes it from siblings like wordpress_get_plugins (likely all plugins) and wordpress_get_plugins_detailed.

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: call this when you need active plugins only. However, it does not explicitly mention when to use it versus other plugin-related tools (e.g., 'use wordpress_get_plugins for all plugins'), leaving differentiation to the name.

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