Update PHP version

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

Annotations already signal mutation and destructiveness, so the description does not need to restate that. It adds a useful prerequisite by pointing the agent to Get PHP details for available versions, but it does not clarify other behavioral aspects such as side effects on the running site or expected confirmation.

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 two short sentences with no filler. The main action is front-loaded and the prerequisite instruction is separated cleanly.

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 with no output schema, the description gives the action and the key prerequisite (check available versions). It is nearly complete, though it would be stronger if it mentioned the difference from agency-hosting_updateWebsitePHPVersionV1 or the destructive consequence of switching versions.

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 description coverage is 100%, so the schema carries the parameter documentation. The description adds no new detail about username, domain, or version; it only reiterates the overall action at the parameter level, which is adequate but not additive.

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 uses a specific verb and resource: 'Changes the PHP version of the website.' It clearly identifies the tool's core operation, though it does not differentiate it from the sibling agency-hosting_updateWebsitePHPVersionV1 or from related PHP update tools.

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 one explicit usage instruction: call the Get PHP details endpoint to discover available versions before switching. However, it does not discuss when to prefer this tool over related PHP tools (options, extensions, agency variant) or state any exclusions.

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