Install WordPress Plugins

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Install plugins by slug' only names the action; it does not disclose side effects (e.g., whether existing plugins are overwritten), required permissions, or whether installation of a plugin is reversible. This is a significant transparency gap for a mutation tool.

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 extremely concise at four words and front-loads the core action. It is not padded with redundant information. It could be slightly more informative while remaining succinct, but it is appropriately sized for a simple tool.

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?

Despite a simple tool, there are no annotations, no output schema, and initial schema descriptions are minimal. The description does not explain how 'username' and 'software' are used, what happens upon successful installation, or how errors are surfaced. This is insufficient for an AI agent to invoke the tool confidently.

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 description covers 100% of parameters, with 'plugins' described as 'Plugin slugs to install'. The description's phrase 'by slug' adds slight reinforcement but no new semantic detail beyond the schema. Baseline 3 is appropriate because the schema already carries the load.

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 'Install plugins by slug' uses a specific verb and resource, clearly indicating an installation operation. It distinguishes itself from siblings like wp_plugins_activate, wp_plugins_deactivate, and wp_plugins_uninstall by focusing on installation. However, it could be more precise about the target (e.g., a specific WordPress installation), so it does not quite reach a 5.

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 such as wp_plugins_activate or wp_plugins_update. The description does not mention prerequisites, such as an existing WordPress installation, or any exclusions. The context is entirely implied by the name and sibling list.

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