wordpress_list_plugins

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

With no annotations provided, the description carries the full burden but only minimally discloses what data fields are returned. It fails to indicate whether this is a safe read-only operation, mention pagination behavior, or explain what constitutes 'details' in the output.

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 brief and front-loaded with the core action. While the '[UNIFIED]' prefix is metadata noise, the two sentences efficiently convey the tool's function without excessive 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?

Given the lack of output schema and 0% parameter description coverage, the description is insufficient. It hints at return fields but provides no documentation for the two input parameters, leaving critical usage information missing.

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 0%, yet the description does not compensate. It mentions 'status' only in the context of output data (active/inactive), failing to explain the input 'status' filter parameter or the required 'site' parameter (e.g., whether it expects a URL, ID, or slug).

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 tool 'List[s] installed WordPress plugins' and identifies what data is returned (status, version, details). However, it fails to distinguish from the sibling tool 'wordpress_wp_plugin_list_detailed', leaving ambiguity about which to use.

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 versus 'wordpress_wp_plugin_list_detailed' or other WordPress plugin tools. The description does not explain the input filtering capabilities or prerequisites for the 'site' parameter.

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