List WordPress Themes

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

Beyond the annotations (readOnlyHint=true, destructiveHint=false), the description adds critical behavioral context: the admin capability requirement, the 403 response for non-admins, the active theme flag, and child theme detection logic. It also details the return object's shape. This goes well beyond what annotations alone provide.

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 well-structured, starting with the core purpose, followed by a brief behavioral note, then clearly formatted args and returns. Every sentence provides necessary information, with no fluff or redundancy. It is front-loaded and easy to scan.

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 list tool with two optional parameters, the description is fully complete. It covers the return shape, auth requirements, and behavioral nuances, while the schema handles parameter definitions. No significant information is missing given the tool's low complexity.

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 input schema already provides 100% coverage with detailed descriptions, enums, and defaults for both parameters. The description repeats this information without adding new semantics. Given the high schema coverage, a baseline of 3 is appropriate.

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 opens with 'List installed themes,' which is a specific verb+resource that clearly states the tool's function. It distinguishes itself from sibling tools like wp_list_plugins or wp_list_posts by focusing on themes, and adds useful distinguishing details like active theme flagging and child theme detection.

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 description provides clear context for when to use this tool: to list installed themes, with notes about active status and child theme detection. It also warns about the admin capability requirement. However, it doesn't explicitly mention alternatives or when not to use it, so it stops short of a 5.

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