List available WordPress versions

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful context beyond those annotations by clarifying the scope: it lists versions available for installation and is tied to Agency Plan websites, differentiating it from update-related and PHP-version siblings.

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?

One sentence with no filler. It front-loads the core action, then adds the two key qualifiers: "WordPress core versions" and "Agency Plan website," which are necessary for correct tool selection.

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 read-only list operation with one fully documented parameter and a safety profile already covered by annotations, nothing needed to call this tool correctly is missing. The lack of an output schema is not a gap because the return value is self-evident from the name and description.

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 required parameter, website_uid. The description adds no parameter-specific detail, but the schema already fully documents the parameter, so the baseline of 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 states a specific verb and resource: "Lists the WordPress core versions available for installation on an Agency Plan website." It clearly distinguishes itself from related siblings like hosting_listAvailableWordPressCoreUpdatesV1 by specifying installation availability 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?

The description makes the use case clear: an agent should call this when it needs WordPress core versions available for installation on an Agency Plan website. It does not explicitly name alternatives or when-not-to-use conditions, but the qualifiers are strong enough that an agent can route to this tool correctly.

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