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

Annotations already declare read-only/idempotent/open-world, yet the description adds real substance beyond them: null semantics for tested_up_to, that modified_at is UTC and refers to the main plugin file, network_active only on multisite, and the operational meaning of must-use and drop-in plugins. This is exactly the kind of behavior an agent needs to interpret results correctly.

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?

Front-loaded with the verb and scope, then the return-field enumeration, then the usage rationale. The long run-on field list is dense but every item maps to actual output content, so it earns its space; slightly tighter grouping would improve it.

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?

No output schema exists, so the description must describe return values — and it does, enumerating every field with edge-case semantics (nulls, multisite, UTC). Combined with the read-only note and debugging rationale, an agent has everything needed to call and interpret it.

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?

There is a single optional site_id parameter fully documented in the schema (100% coverage, single-value enum), so the schema carries the burden. The description reinforces it with '(site: demo.royalplugins.com)', adding no ambiguity, though it adds little beyond what the enum already communicates.

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?

States a specific verb and resource ('List all installed plugins') and expands scope to include must-use plugins and drop-ins, which an agent could not infer from the name. It does not, however, distinguish itself from near-identical siblings such as fleet__list_plugins, mcp-easy-ai__wp_list_plugins, or mcp-tools-for-elementor__emcp-tools-list-plugins.

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?

Gives a clear usage context: diagnosing plugin conflicts and building a compatibility picture 'at the start of a debugging conversation.' That is actionable guidance, but there are no exclusions or explicit pointers to the sibling plugin-listing tools that would tell an agent when not to use this one.

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