Install Plugin

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

Discloses important behaviors beyond the annotations: requiring exactly one source, the semantics of activate, and refusal on production without confirm_production. It does not mention potential side effects of overwriting existing plugin files, but since destructiveHint=false, this is not a direct contradiction and the provided detail is substantive.

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 long, front-loaded with the primary action, and every phrase adds value: source options, update alternative, activation flag, and production safety condition. No wasted words.

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?

Given the complexity of 8 parameters with four mutually exclusive source options, the description covers the essential selection logic, activation behavior, update fallback, and production guard. It does not explain return values, but no output schema exists and the description is sufficient for an agent to invoke the tool 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 provides 100% coverage with parameter descriptions, but the tool description adds critical meaning by explaining the relationship among source parameters ('Pick ONE source') and clarifying how overwrite relates to updates. This goes beyond what the schema alone conveys.

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 'Install a plugin on the target WordPress site,' using a specific verb and resource. It also differentiates from the sibling tool wp_update_plugin by explicitly naming it as the preferred tool for updates.

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?

Provides explicit when-to-use guidance: 'For updating an already-installed plugin, use wp_update_plugin instead (or pass overwrite=true here).' It also explains the production guard, making it clear when confirm_production is required and mentioning source selection constraints.

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