wp_install_quick

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

With no annotations, the description must carry the full burden of behavioral disclosure. It conveys that an installation happens, which implies mutation, but it does not disclose side effects, whether existing installations are overwritten, what the 'confirm' flag controls, or what resources are created or modified. The 'confirm: Required' note adds confusion instead of clarity.

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 and front-loaded, which supports conciseness. However, the 'confirm: Required' line is misleading and the argument notes add little meaningful information, so not every element earns its place.

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 installation tool with an opaque nested payload and no annotations, this description is too incomplete to call safely. It does not explain the payload contract, the role of confirm, or how this relates to wp_install. The presence of an output schema reduces the need for return-value details, but the input side remains severely underspecified.

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 description coverage is 0%, so the description must compensate, but it only labels payload as 'Quick-install body' and confirm as 'Required.' This is too vague to determine what fields the payload should contain or what confirm actually does. It also contradicts the schema: confirm is described as required but the schema lists only payload as required.

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 concrete action and resource: 'Quick WordPress install.' It clearly identifies the tool as an installer for WordPress, and the 'quick' qualifier hints at a distinct variant from the sibling wp_install. However, it does not explain what makes this install quick or how it differs from the regular install.

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 given on when to use this tool versus wp_install or any other alternative. There is no mention of preconditions, exclusions, or situations where a different install flow should be chosen. The word 'quick' only weakly implies a use case.

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