Set Wordpress Php Version

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

Annotations already declare non-read-only, idempotent, destructive, so the description doesn't need to restate safety. It adds valuable behavior the annotations can't: propagation delay ('within a minute or two') and an explicit rollback path ('switch back the same way') for a destructive change.

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 short sentences, front-loaded with the action, then the constraint, then the timing and confirmation requirement. No repetitive or filler wording.

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 destructive, no-output-schema mutation with fully documented parameters, this covers action, constraint, propagation, and rollback. Only minor gaps remain, such as not restating that changes are idempotent or what a failure surfaces as.

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 100%, so baseline is 3. The description adds real meaning beyond the schema by tying `version` to the allowed set returned by get_hosting, which the schema only hints at. `dry_run` is left to the schema description, which covers it adequately.

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: 'Change the PHP version a Cloud for WordPress site runs.' The qualifier 'PHP' cleanly separates it from the sibling set_wordpress_version, and no ambiguities remain about what is being mutated.

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?

Gives concrete prerequisites (version must come from availablePhpVersions via get_hosting) and a procedural instruction (confirm with the user first), plus a recovery path. It stops short of naming when-not-to-use conditions or an alternative approach beyond rollback.

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