WordPress: Wp theme list

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real value beyond that: a bridge version floor and a capability requirement (manage_options) that determine whether the call works at all, plus the exact field set returned. It does not discuss whether inactive/child themes are all included or what happens with an invalid site.

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?

Very compact: one sentence covering what is listed and the returned fields, one sentence covering prerequisites. Zero waste overall, though the '[UNIFIED]' prefix is internal jargon that consumes attention without informing the agent.

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 tool with no output schema, the description effectively substitutes for one by naming every returned field. The main remaining gap is the undocumented 'site' parameter format, which matters because it is the only input.

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?

Only one parameter (site) and the schema description coverage is 0%, so the schema tells the agent nothing about it. The description does not compensate — it never explains what 'site' expects (ID, slug, URL). The requirement line hints at an authenticated bridge context but not the identifier format.

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 (List) and resource (every installed theme) and enumerates exactly what is returned: stylesheet/template names, version, parent, block-theme flag, active flag, update availability. That distinguishes it from the theme_file_list sibling by making clear it returns theme records rather than file paths, though it never names the alternative explicitly.

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?

Usage is only implied — you call it when you need an inventory of installed themes. There is no explicit when-to-use, no exclusion, and no pointer to wp_theme_file_list for file-level inspection. The prerequisite line (Airano MCP Bridge v2.11.0+ and manage_options) is genuine guidance about when the call can succeed.

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