wp_list_plugins

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the output fields (status, version, update availability) but does not explicitly confirm this is a read-only operation, nor does it mention error handling, pagination, or potential side effects. The verb 'list' implies safety, but that is not made explicit.

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, concise sentence that states the core purpose and the key output fields. It is front-loaded with the main action and resource, and contains no unnecessary wording—every part earns its place.

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 low complexity (no parameters, no annotations, no output schema), the description adequately covers what the tool does and what information it returns. It stops short of describing the return format or pagination behavior, but for a simple list tool, the provided details are largely sufficient for an agent to understand the call.

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, so there is nothing to document. The baseline for 0-param tools is 4, and the description appropriately adds no parameter-related content, avoiding redundancy with an empty schema.

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 is highly specific: it names the resource ('installed WordPress plugins'), the action ('List'), and the exact details returned (status, version, update availability). This clearly distinguishes it from sibling tools like wp_search_plugins, wp_install_plugin, or wp_list_themes based on its verb and 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?

The description provides no explicit guidance on when to use this tool versus alternatives such as wp_search_plugins or other list tools. There is no mention of scenarios where searching is preferable or when this tool is the right choice, leaving the agent to infer usage from the name alone.

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