Set Wordpress Version

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds real value beyond them by explaining the lasting consequence of `previous` (no newer releases until reset to `latest`) and the duration ('takes a few minutes'). It stops short of stating whether the site experiences downtime during the change or what permissions are required.

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?

Compact and front-loaded: the core action comes first, the mode semantics follow, and the duration note closes it. Every clause carries information, with no filler.

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 three-parameter mutation tool with no output schema, the description covers the action, the value semantics, the reversibility path, and the expected latency. Minor omissions are the on-disk outcome details and any prerequisite like site health or staging state.

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 67% and the `version` enum has no per-value description in the schema; the description compensates thoroughly by defining `latest` vs `previous` and ruling out pinned version numbers. `domain` and `dry_run` are already documented in the schema, so no duplication is needed.

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?

States a specific verb and resource (set a Cloud for WordPress site's WordPress version) and immediately defines the only two allowed values with their semantics. The agent knows exactly what the tool changes, distinct from siblings like set_wordpress_php_version or set_wordpress_search_visibility.

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 frames `previous` as 'the escape hatch when an update breaks the site', giving a concrete condition for choosing it over `latest`. It does not name adjacent siblings (e.g. rollback or staging tools) as alternatives, but the when-to-use guidance for the two modes is clear.

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