list-plugins

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

With no annotations, the description must carry the transparency burden. 'List' implies a non-destructive read operation, and 'activation status' indicates return content, but nothing is disclosed about authentication, error handling, or pagination behavior. It covers the basic safety profile but no more.

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, front-loaded sentence that contains only essential information. No wasted words; it's as concise as possible while still being informative.

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 is a simple list operation with a clear purpose and fully documented parameters. The description omits explicit output structure, but 'list plugins with activation status' implies an array of plugins with status, which is sufficient for invocation. Slightly incomplete due to no mention of default pagination, but the schema covers 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?

Schema description coverage is 100%, so parameters are already well-documented. The description does not add additional meaning to any parameter, just restates that plugins and activation status are involved. Baseline 3 is appropriate.

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 a specific verb ('List') and resource ('installed WordPress plugins'), with additional detail ('activation status') that clearly distinguishes it from sibling list tools like list-posts or list-media. Purpose is unambiguous.

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 implies usage—when you need to see installed plugins and their status, this is the tool—but provides no explicit alternatives, exclusions, or contextual guidance. There are no sibling plugin-specific tools competing, so it's adequate but not explicit.

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