wordpress_wp_core_update

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

No annotations provided, so description carries full burden. Discloses critical behavioral traits: default dry-run safety mode, requires explicit opt-in to apply changes, and warns about backup requirements implying destructive risk. Missing rollback or failure behavior details.

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?

Front-loaded with purpose, followed by critical safety mechanism, then imperative warning. Every sentence earns its place. Minor deduction for '[UNIFIED]' metadata tag which adds slight clutter without clear value in this context.

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 high-risk mutation operation with no annotations and no output schema, the description covers the essential safety guardrails (dry-run default, backup requirement). Adequate completeness given the tool's simplicity, though could benefit from mentioning what the dry-run output contains.

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 coverage is 0%, requiring description to compensate. Explains dry_run parameter behavior excellently ('Set dry_run=false to apply updates'). However, does not explain 'version' (target version vs latest?) or 'site' parameters, leaving gaps in parameter understanding.

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?

Description clearly states 'Update WordPress core' with specific verb and resource. It distinguishes from sibling plugin/theme update tools by specifying 'core'. The [UNIFIED] tag aside, the purpose is unambiguous.

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 guidance on the dry_run toggle: default shows available updates, set false to apply. Includes critical backup warning. Lacks explicit naming of sibling alternatives (e.g., verify_checksums), but covers the essential safety workflow.

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