List Available Plugins

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

Without annotations, the description carries the full burden of behavioral disclosure, but it only states a basic listing action. It does not mention that the operation is read-only, nor does it disclose permissions, rate limits, or the structure of 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?

The description is a single, focused sentence with no redundant words or filler. It is concise and front-loaded, making it easy to parse.

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 description is minimal and leaves out important context such as what 'available' means exactly (e.g., from the WordPress repository vs. pre-uploaded options), the output format (since no output schema exists), and whether any preconditions exist. This is particularly important given the absence of annotations and output schema.

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 already provides descriptions for both parameters (100% coverage), so the baseline is 3. The description itself adds no extra meaning to the parameters, and the schema's phrase 'WordPress software identifier' is still somewhat vague, but the schema coverage means the description does not need to compensate much.

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 uses the specific verb 'List' and identifies the resource as 'plugins available for installation', which clearly distinguishes it from sibling tools like wp_plugins_list (likely lists installed plugins) and wp_plugins_search. The scope is implied via 'available for installation', but it is minimal and does not elaborate on the source or criteria.

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?

No guidance is provided on when to use this tool versus alternatives like wp_plugins_search or wp_plugins_suggested. There are no exclusions, prerequisites, or contextual notes that would help an agent decide the appropriate scenario for selection.

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