install_plugin

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

No annotations are provided, so the description carries full burden. It only says 'install and activate' without disclosing side effects (e.g., permission requirements, whether it overwrites existing installations, or what happens on failure).

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?

One sentence clearly stating the action. No unnecessary words, but could be expanded slightly for clarity without losing conciseness.

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?

No output schema, no annotations. The description lacks behavioral context such as what happens if the plugin is already installed, if it requires authentication, or what the return value contains. Incomplete for a tool that modifies system state.

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 has 2 parameters: 'site' (described in schema) and 'slug' (no description in schema, 50% coverage). The description adds no extra meaning beyond the schema for either parameter. The slug parameter is left entirely to inference from the tool name.

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 clearly states the action: 'Install and activate a plugin from the WordPress ecosystem.' It specifies the verb (install and activate) and resource (plugin), and distinguishes from siblings like 'activate_plugin' which only activates a presumably already installed plugin.

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 (e.g., activate_plugin for already installed plugins, or when prerequisites like authentication are needed). The description only states the function without context-specific conditions.

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