List plugins

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

The description discloses the Administrator account requirement, which is not present in the annotations, and explains that lower roles receive no data. It also specifies that the output includes activation status and version. This adds meaningful behavioral context beyond the readOnlyHint and destructiveHint annotations.

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 two sentences with no redundancy. The core function is front-loaded in the first sentence, and the second sentence adds the necessary permission context. Every word earns its place.

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 read-only list tool with three optional parameters and no output schema, the description covers the essential requirements: it states the scope ('every plugin'), the return fields (status and version), and a critical permission constraint. It lacks pagination details, but the description is sufficient for an agent to call it 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%, with all three parameters (search, status, site_id) fully described in the input schema. The description adds no additional parameter semantics or syntax details, so the baseline of 3 applies.

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 explicitly states 'List every plugin installed on the site with its activation status and version', which is a specific verb+resource with clear output details. It differentiates from sibling tools like search_plugins by emphasizing 'every' and from get_plugin by being a list operation. The admin requirement further clarifies the scope.

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 does not explicitly contrast with sibling tools such as search_plugins or get_plugin, nor does it state when to prefer this over alternatives. It implies usage for enumerating all plugins, and the admin requirement acts as a precondition, but there is no explicit directional guidance.

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