wp_list_themes

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

No annotations are provided, so the description carries the full disclosure burden. It conveys only that this is a listing operation; it does not mention permissions required, whether inactive/child themes are included, multisite behavior, or result volume. For a tool with zero annotation coverage this is thin.

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, front-loaded sentence with no filler, appropriate for a simple list tool. It is efficient, though it errs toward under-specification rather than tight conciseness.

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 a simple read-only listing with a complete two-parameter schema and no output schema, so requirements are modest. Still, with no annotations, the description should at minimum confirm it is a safe read and clarify the scope of 'all' (active vs inactive), which it does not.

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%, with both 'site' (referencing list_sites) and the 'status' enum fully documented in the schema, so the baseline is 3. The description adds no parameter-level meaning (e.g. default status behavior when the filter is omitted) beyond what the schema already states.

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?

States a specific verb and resource ('List all installed themes'), so an agent immediately knows the operation. However it does nothing to differentiate itself from close siblings such as wp_get_theme, wp_get_active_theme, or mcp_search_themes, which a caller must disambiguate by introspection.

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 on when to call this rather than wp_get_theme (single theme detail), wp_get_active_theme (current theme only), or mcp_search_themes (theme repository search). The only hint of scope is the word 'all', which is not framed as an exclusion.

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