wp-cli-mcp

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states 'Execute any WP-CLI command directly' but doesn't disclose permissions needed, potential destructive effects, rate limits, error handling, or output format. For a powerful raw execution tool, this is inadequate disclosure.

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, efficient sentence that immediately conveys the core functionality. There's zero wasted verbiage, and it's perfectly front-loaded with the essential information.

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 that executes arbitrary WP-CLI commands with no annotations and no output schema, the description is insufficient. It doesn't explain what kind of output to expect, error conditions, safety considerations, or how this differs from the many specialized sibling tools. The context demands more guidance than provided.

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?

Schema description coverage is 100% with the single 'command' parameter well-documented in the schema. The description adds no additional parameter semantics beyond what the schema already provides (e.g., no examples beyond the schema's example, no clarification of command syntax rules). Baseline 3 is appropriate when schema does the heavy lifting.

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 verb ('Execute') and resource ('any WP-CLI command'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like wp_db_query or wp_search_replace, which also execute specific WP-CLI commands but with predefined functionality.

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 no guidance on when to use this tool versus the many specialized sibling tools. It doesn't mention alternatives, prerequisites, or appropriate contexts for raw command execution versus using specific tools like wp_post_create or wp_plugin_activate.

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