agency-hosting_updateWebsitePHPVersionV1

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

With no annotations, the description carries full transparency burden. It discloses that 'the website restarts on the new version, so requests served during the switch may fail and code that is incompatible with the target version will break,' providing critical side-effect information about downtime and breakage.

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 concise sentences: it states the purpose first, then provides behavioral warnings. Every sentence adds meaningful information without fluff, making it well-structured and front-loaded.

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 the tool's simplicity (2 required parameters, no output schema), the description covers the essential aspects: purpose, prerequisite, and side effects. It could mention the expected result on success, but it is complete enough for typical usage.

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 schema already provides descriptive text for both parameters: version includes 'PHP version to switch the website to, as major.minor' and 'Must be one of the versions returned by the available versions endpoint,' and website_uid explains its purpose. The description adds no new parameter semantics beyond what the schema provides, so a baseline 3 is appropriate.

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 clearly states 'Switches an Agency Plan website to a different PHP version,' using a specific verb and resource. The 'Agency Plan' qualifier distinguishes it from the generic hosting_updatePHPVersionV1 sibling, providing clear purpose.

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?

It instructs to 'Call the available versions endpoint first to see which versions can be selected,' which is a concrete prerequisite. However, it doesn't explicitly name alternatives, though the 'Agency Plan' qualifier implies it's for Agency Plan sites, differentiating from the non-agency sibling.

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