wp_plugin_list

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

With no annotations, the description reveals key behaviors: the command executed, default user (www-data) and root option, read-only nature, and 60-second timeout. This covers safety and execution context well, though error handling is not mentioned.

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 efficient: four sentences in Dutch (similar length in English) that front-load the purpose and then detail prerequisites, execution, and behavior. No unnecessary words.

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?

The tool has an output schema, so return values are not needed. The description covers prerequisites, parameter behavior, and execution context (timeout, user). It is adequately complete for a read-only list tool.

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%, so the description compensates by explaining site_path must be in allowed sites and contain wp-config.php, and as_www_data controls user context (www-data vs root). This adds meaning beyond type/optionality.

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 it reads installed WordPress plugins of an allowed site (verb 'Lees' + resource 'WordPress-plugins'). It is specific but does not explicitly differentiate from sibling tools like wp_cli which can also run 'wp plugin list'.

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 prerequisites (site_path must be in wp_allowed_sites and contain wp-config.php) and states the operation is read-only. However, it lacks explicit guidance on when to use this tool vs. alternatives (e.g., wp_cli for custom plugin commands).

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