wordpress_plugin_exists

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

No annotations are provided, so the description must fully explain behavior. It only states 'Check if a plugin is installed' without clarifying whether 'installed' means active vs. present, what the return type is, or how errors are handled. This is sparse for a tool that should disclose its exact semantics.

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 with no filler. Every word contributes to stating the tool's purpose, making it appropriately concise for a simple existence check.

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 low-complexity with one parameter and no output schema. The description gives the core action but omits parameter format and return semantics, leaving it minimally viable rather than fully complete. Given its simplicity, the gaps are not severe but do exist.

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 schema has one required string property 'plugin' with no description and 0% schema coverage. The description merely repeats the word 'plugin' and does not explain whether the value should be a slug, folder name, or full path. It adds minimal meaning beyond the schema.

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 'Check if a plugin is installed' uses a specific verb and resource, clearly indicating a boolean existence check. It is distinct from sibling tools like wordpress_get_plugins (which list plugins) and wordpress_get_plugin_status (which reports status), so purpose clarity is strong.

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?

There is no guidance on when to use this tool versus alternatives such as get_plugins or get_plugin_status. No context, prerequisites, or exclusions are provided, leaving the agent to infer usage from the tool name alone.

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