agency-hosting_listAvailablePHPVersionsForAWebsiteV1

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

With no annotations, the description carries the transparency burden. It adds useful context by noting that the current version is returned via the website details endpoint under settings.php.version, but it does not state whether the list includes/excludes the current version or any permissions required.

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 sentences with no filler. The first sentence front-loads the primary action and scope; the second provides relevant cross-reference to the website details endpoint. Every word earns its place.

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 single-parameter list tool without an output schema, the description is nearly sufficient. It explains what is returned (list of PHP versions) and adds context about the current version. However, it could be more complete by explicitly differentiating from the order-based sibling to avoid misuse.

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% for the single parameter (website_uid), so the schema already documents it. The description adds no additional meaning beyond what is in the schema, matching the baseline for high coverage.

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 ('Lists') and resource ('PHP versions an Agency Plan website can be switched to'), clearly stating the tool's function. It differentiates from the order-based sibling by focusing on 'website', but does not explicitly name alternative 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 implies when to use the tool (when you need available PHP versions for a specific website) but provides no explicit alternatives, exclusions, or comparisons with similar tools like listAvailablePHPVersionsForAnOrder. Guidance is only implicit.

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