wp_cli

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

With no annotations, description fully discloses constraints (allowed sites, wp-config.php), shell quoting (no expansion), potential site modification, user context (www-data vs root with --allow-root), timeout (60s), and return values (command, stdout, stderr, exit code). No contradictions.

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?

Description is concise and front-loaded with the main action. Each sentence adds value, covering parameters, behavior, and constraints without unnecessary verbosity.

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?

With an output schema present, description covers all necessary context: prerequisites (site_path constraints), execution behavior (shell quoting, user context, timeout), and result contents. Adequate for the tool complexity.

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 coverage is 0%, but description adds meaning for all three parameters: site_path (required allowed site), args (shell-like quoting without expansion), as_www_data (default true, if false runs as root with --allow-root).

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?

Description clearly states the tool executes WP-CLI arguments on allowed WordPress sites. It differentiates from sibling tools like wp_cache_flush, wp_plugin_list, and wp_user_list by specifying general WP-CLI command execution.

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?

Provides clear prerequisites: site_path must be in wp_allowed_sites and contain wp-config.php. Explains argument quoting behavior and user context options, but does not explicitly state when to use this tool over siblings.

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