wp_install

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. It reveals that this is a mutating install operation, but it does not explain what 'confirm' actually does, whether installation can overwrite existing content, what prerequisites exist, or what side effects may occur. The claim that confirm is 'Required' also conflicts with the schema default of false, adding confusion.

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 very short, front-loaded with the core action, and free of filler. It could be better structured with clearer parameter explanations, but as written it wastes no 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?

For a mutating tool with a nested payload object, no annotations, and a sibling quick-install variant, this description is under-specified. It lacks any distinction from wp_install_quick, explanation of confirm's role, prerequisites, or effects. The presence of an output schema covers return values, but not the missing operational context.

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 payload parameter gains some meaning from 'domain, path, title, admin user, …', which is helpful given the schema's 0% coverage. However, 'confirm' is only labeled 'Required,' which contradicts the schema where it is not required and defaults to false. The description does not explain what confirmation is being requested.

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 clear verb and resource: 'Install WordPress.' This unambiguously identifies the main action. However, it does not differentiate wp_install from the sibling wp_install_quick, so it stops short of 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?

There is no guidance about when to use this tool versus wp_install_quick or other WordPress-related tools. No prerequisites, context, or exclusions are provided. The description only states what the tool does, not when to choose it.

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