wp_list_themes

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

The tool is a simple read operation (listing). The description clearly states it lists 'all installed themes', which is transparent. No annotations are provided, so the description correctly communicates the safe, non-destructive behavior.

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 of 4 words, perfectly concise with no filler. It front-loads the core purpose effectively.

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 listing tool with no output schema, the description is adequate but minimal. It could mention what is returned (e.g., theme names, objects) to compensate for the missing output schema. However, given low complexity, it suffices.

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 description does not add any parameter details beyond what the input schema already provides. Schema coverage is 100% with a description for 'status', so baseline 3 is appropriate; no extra value from description.

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 'List all installed themes' uses a clear verb ('List') and resource ('themes'), with an implicit scope of 'all installed'. It distinguishes from siblings like 'mcp_search_themes' (search/filter) and 'wp_get_active_theme' (single theme).

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 use this tool versus alternatives (e.g., 'mcp_search_themes' for filtering, 'wp_get_active_theme' for a specific theme). The description provides no context for selection.

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