wp_search_plugins

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It clearly indicates a search against an external directory and implies no installation occurs, but it does not explicitly state that it is read-only, describe rate limits, or mention network dependence. This is adequate for a simple search but not fully transparent.

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 concise sentences with no filler. The primary purpose is front-loaded, and the usage context is given immediately, making it easy for an agent to parse quickly.

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 simple search tool with only two parameters, the description covers what the tool does, how it relates to the install workflow, and the query target. It does not describe return value structure, but no output schema exists and the tool's purpose is straightforward enough that an agent can infer the expected result.

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 both 'query' and 'per_page' are already documented in the schema. The description adds only the general 'by name or keyword' hint, which aligns with the query parameter but does not substantively improve parameter understanding.

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 ('Search'), a clear resource ('WordPress.org plugin directory'), and the intended workflow context ('before installing them'). This distinguishes it from sibling tools like wp_list_plugins (installed plugins) and wp_install_plugin (installation), so an agent can route appropriately.

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 phrase 'Use this to find plugins by name or keyword before installing them' provides clear usage context and implies it is the discovery step prior to installation. It does not explicitly name alternative tools or exclusion cases, but the context and sibling list make the intended usage reasonably clear.

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