List available PHP versions for a website

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

Annotations already indicate this is read-only and non-destructive, and the description adds a useful note that the current PHP version is available from the website details endpoint. However, it does not describe the response format, availability semantics, or pagination, so it adds only modest behavioral context beyond the annotations.

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?

Two short sentences deliver the core purpose and a valuable pointer to related data, with no filler. The main action is front-loaded and the second sentence earns its place by helping the agent locate the current PHP version.

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 simple one-parameter read-only list with annotations already covering safety, the description is largely sufficient. A brief mention of the response shape or the order-level sibling tool would make it complete, but nothing essential blocks correct invocation.

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 documents the single parameter as an Agency Plan website UID, so the description does not need to add much. The mention of 'Agency Plan website' in the description mostly restates the schema and supplies no examples, constraints, or additional formatting guidance.

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 states a specific action ('lists') and resource ('PHP versions an Agency Plan website can be switched to'), making the purpose immediately clear. It distinguishes itself from extension/option listers through the 'can be switched to' scope, though it does not explicitly contrast with the similar order-level PHP-versions sibling.

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 gives a concrete use case: finding which PHP versions an Agency Plan website can switch to. It does not mention when not to use it or point to the order-level alternative, but the website-specific framing provides clear context without being misleading.

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