wordpress_wp_plugin_list_detailed

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

With no annotations provided, the description carries the full burden. It usefully enumerates what data is returned (versions, status, updates), confirming the read nature of the operation. However, it lacks disclosure on authentication requirements (likely admin-level), rate limits, or whether 'available updates' triggers external API calls.

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?

Single sentence is efficient and front-loaded with the key action. However, the '[UNIFIED]' prefix appears to be implementation metadata leaking into the description and adds no semantic value for the agent.

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?

For a single-parameter list operation without output schema, the description adequately explains the return value contents (fields included). However, completeness is hampered by the complete omission of the 'site' parameter semantics and lack of behavioral safety details (read-onlyHint would normally cover this).

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% for the required 'site' parameter. The description fails to compensate by explaining what 'site' should contain (URL, domain, ID), what format is expected, or providing an example. The parameter meaning must be inferred from the context.

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 action (List), resource (WordPress plugins), and scope (all plugins with detailed versions, status, and available updates). The specific field enumeration distinguishes this from the sibling tool `wordpress_list_plugins` (presumably basic) and from mutation siblings like `wordpress_wp_plugin_update`.

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 term 'detailed' implies usage context (when comprehensive plugin data is needed), but there is no explicit guidance on when to choose this over the simpler `wordpress_list_plugins` sibling, nor any prerequisites mentioned.

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