wp_list_themes

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

With no annotations provided, the description carries the full burden and does disclose what the agent will receive (active/inactive status, version, parent theme), implying a read-only enumeration. However, it does not address contextual behavior such as WordPress multisite semantics (network-active vs site-active themes), output format, or any permissions needed to enumerate themes.

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?

A single 18-word sentence with zero waste: the verb and resource are front-loaded, and the return fields are listed compactly. Every clause 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 low-complexity, zero-parameter tool with no output schema, the description adequately conveys the result contents (status, version, parent theme info), compensating for the missing output schema. The main gaps are the lack of comparative guidance versus wp_search_themes and no annotation coverage to confirm the read-only safety profile.

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 tool has zero parameters, so the baseline is 4; the description correctly implies a no-input operation and adds no misleading parameter claims. Since there is nothing to document, the description provides appropriate meaning for the empty schema.

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 ('List') and resource ('all installed WordPress themes') with explicit scope ('all installed'), which distinguishes it from siblings like wp_search_themes, wp_install_theme, and wp_activate_theme. It also enumerates the specific fields returned (status, version, parent theme info). An agent can tell exactly what this tool does without opening any schema.

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 phrase 'List all installed' implies the use case of enumerating the full theme inventory, but there is no explicit when-to-use guidance or exclusion. With wp_search_themes as a close sibling, the description misses the opportunity to route the agent ('to find a theme by criteria, use wp_search_themes instead'), leaving selection to inference.

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