wordpress_wp_theme_update

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

No annotations provided, so description carries full burden. Effectively discloses dry-run default behavior and warns that 'Updating active theme can break site appearance!' Missing disclosure on rollback capabilities, failure modes, or whether backups are created automatically.

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?

Three sentences with zero waste: '[UNIFIED]' marker, purpose with dry-run behavior, and safety warning. Front-loaded with essential operational context before the warning.

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?

Adequate for a mutation tool with no output schema: safety warning present, dry-run pattern explained. Incomplete due to undocumented parameters and lack of description for return values or success indicators (e.g., whether it returns update logs or version confirmations).

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% (no parameter descriptions). Description compensates only for dry_run behavior implicitly. Critical parameters 'site' and 'theme_name' are completely undocumented—no indication if theme_name expects a slug, directory name, or display name, or what format 'site' requires.

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?

Clear verb 'Update' and resource 'WordPress theme(s)', with default dry-run behavior distinguishing it from immediate-application tools. Minor ambiguity with plural '(s)' versus singular 'theme_name' parameter. Does not explicitly differentiate from sibling listing tools like wordpress_wp_theme_list_detailed.

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?

Explicitly documents the dry_run toggle usage (default true for preview, false to apply) and warns about risks with active themes. Lacks guidance on prerequisites (e.g., verifying theme exists beforehand) or when to use versus theme inspection/listing siblings.

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