agency-hosting_listAvailableWordPressVersionsV1

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

There are no annotations, so the description carries the full burden. 'Lists' implies a read-only operation, and the resource and scope are stated, but no behavioral details are disclosed about output format, sorting, pagination, or any prerequisites beyond the website_uid parameter.

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 a single sentence with no fluff or redundancy. It communicates the core purpose, resource, and scope efficiently.

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 list operation with one parameter and no output schema, this description is largely sufficient: it states what will be returned and for what target. Minor gaps exist around response format or availability criteria, but these are not critical for a basic listing tool.

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%, and the single parameter website_uid is already clearly described as 'Agency Plan website UID'. The tool description adds no additional meaning to the parameter, so the baseline score of 3 applies.

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') with a clear resource ('WordPress core versions available for installation') and scope ('Agency Plan website'). It also differentiates from sibling tools like hosting_listAvailableWordPressCoreUpdatesV1 by focusing on installation rather than updates.

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?

No explicit guidance is given for when to use this tool versus alternatives such as hosting_listAvailableWordPressCoreUpdatesV1 or agency-hosting_changeWordPressVersionV1. The intended use is only implied by the phrase 'available for installation' rather than stated as a recommendation or exclusion.

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