List installed WordPress plugins

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context by disclosing that results include plugin status, available updates, and known vulnerabilities, which helps an agent set expectations about the returned data.

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?

Two well-structured sentences with no fluff. The core purpose is front-loaded, followed immediately by the most important operational detail: how to obtain the required identifier.

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 straightforward read-only listing operation, the description covers the operation, key output aspects, and how to source the required path identifier. It does not specify response shape, but there is no output schema and the coverage is reasonable for an agent to select and invoke the tool correctly.

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 100%, so the baseline is 3. The description adds useful context for the 'software' parameter by explaining it is the WordPress installation identifier and where to find it, but it does not clarify the purpose of 'username' beyond the schema's generic 'username parameter' text.

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 states a specific verb ('List'), a specific resource ('plugins installed on a WordPress installation'), and the content returned (status, updates, vulnerabilities). The word 'installed' distinguishes it from sibling tools like hosting_listAvailableWordPressPluginsV1 and hosting_searchWordPressPluginsV1.

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 gives a concrete how-to for obtaining the required software identifier, which is useful operational guidance. However, it does not explicitly say when to choose this tool over related plugin listing tools such as listAvailable, listSuggested, or search, nor does it state exclusions.

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