Update PHP Version

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action without noting potential side effects like downtime, version compatibility risks, or whether it alters only the version and not other PHP settings.

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 one concise sentence with no wasted words, immediately conveying the core purpose. It is front-loaded and appropriately sized.

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?

Given no annotations, no output schema, and a terse description, the tool lacks essential context for safe usage. It does not mention impact on the website, validation of the version, or how it relates to the other PHP update tools in the sibling list.

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?

The input schema fully describes all three parameters (domain, version, username) with 100% coverage. The description adds no additional parameter detail, so it meets the baseline where the schema does the heavy lifting.

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 'Change PHP version for a website' clearly identifies the action and resource. It is specific enough to distinguish from general hosting operations, though it does not explicitly reference sibling tools like hosting_php_update_extensions or hosting_php_update_options.

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?

The description provides no guidance on when to use this tool versus the related PHP management tools. It lacks any mention of prerequisites, such as checking the current version via hosting_php_details, or exclusions like not being for extension changes.

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