List WP Versions

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

No annotations are provided, so the description carries the full burden. It states the action but does not explicitly disclose whether it is read-only, the response format, or any side effects. The verb 'List' weakly implies a read operation, but this is not stated.

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 concise sentence that states the core purpose with no filler. It is front-loaded and efficiently communicates the tool's function.

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?

The tool is simple with one parameter and no output schema, but the description lacks information about the return format (e.g., array of version strings) and how it relates to version-changing tools like agency_wp_change_version. It also does not explicitly differentiate from wp_list_updates, leaving some ambiguity in context.

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 has 100% coverage for the single parameter (website_uid). The description adds context by implying the UID must belong to an Agency Plan website, which helps interpret the parameter's meaning beyond the schema's generic 'Website UID'.

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 ('List') and resource ('available WordPress versions') with a scope qualifier ('for an Agency Plan website'). This clearly distinguishes it from siblings like wp_get_version (current version) and wp_list_updates (available 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 guidance is provided on when to use this tool versus alternatives like agency_wp_change_version or wp_list_updates. The phrase 'for an Agency Plan website' indicates audience rather than usage conditions, leaving the agent without clear selection criteria.

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