wp_list_plugins

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

The description indicates a read operation (list). No annotations are provided, so the description carries the burden. While it correctly implies no destructive side effects, it does not disclose output format, pagination, or whether the list includes metadata beyond names. It is adequate but lacks depth.

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 extremely concise at 4 words. Every word is necessary. It could be improved by adding a brief mention of optional filtering, but it is efficient and front-loaded.

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 simplicity of the tool (only one optional parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but does not explain return values, scope, or edge cases. For a listing tool, it could be more complete.

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 input schema has 100% description coverage for the only parameter 'status'. The description does not add any meaning beyond what the schema already provides (enum values and description). No additional context is given.

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 action 'List' and the resource 'all installed plugins'. It is specific and unambiguous. However, it does not explicitly differentiate from sibling tools like wp_get_plugin or mcp_search_plugins, but the context implies it lists all plugins rather than searching or getting details.

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 alternatives. For example, it does not mention that to get details of a specific plugin, one should use wp_get_plugin, or that for installing plugins, other tools exist. No exclusions or context are given.

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