Update WordPress Core

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 doesn't mention potential side effects, whether the update is a background process, if it could overwrite customizations, or any required permissions. The word 'update' implies mutation, but no safety or risk cues are given.

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 a single, clear sentence with no filler. It gets straight to the point. However, it could arguably be slightly more detailed while still remaining concise, but the brevity is acceptable given the simplicity of the operation.

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?

The description lacks critical context for a mutation tool. There is no output schema or annotations to supplement it. It doesn't explain what happens after the update, whether it's reversible, or what the response looks like. For a tool that modifies a WordPress installation, this feels incomplete.

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?

Both parameters are fully described in the schema (username and software with clear descriptions), so parameter semantics are adequately covered. The description adds no extra meaning beyond the schema, but the baseline of 3 applies given the 100% schema coverage.

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 ('Update'), the target ('WordPress core'), and the specific goal ('to latest version'). This distinguishes it from sibling tools like wp_plugins_update or wp_themes_update. Verb+resource+scope are all present.

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 vs alternatives. It doesn't mention checking for available updates with wp_list_updates first, nor any prerequisites like WordPress being installed. The description simply states the action without context.

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