wp_get_theme

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

No annotations are provided, so the description must fully convey behavioral traits. It indicates a read operation ('Get'), but does not disclose what happens if the theme does not exist, whether authentication is required, or any side effects. The description lacks depth for a mutation-free tool.

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, concise sentence of 6 words. It is front-loaded and contains no fluff. Perfect for a simple tool.

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 tool with one required parameter and no output schema, the description tells the action and input but does not specify what 'theme details' includes or how errors are handled. It is minimally complete but could be improved with more detail.

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 schema covers 100% of the parameter 'stylesheet' with a description 'Theme stylesheet (folder name)'. The tool description merely repeats 'by stylesheet name', adding no new meaning beyond the schema. 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 'Get theme details by stylesheet name' uses a specific verb ('Get') and resource ('theme details'), and clearly identifies the input (stylesheet name). It distinguishes this tool from siblings like wp_list_themes, wp_get_active_theme, and mcp_search_themes, which have different purposes.

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 does not provide any guidance on when to use this tool versus alternatives. It does not mention when not to use it, nor does it point to siblings like wp_get_active_theme for the active theme. The context is missing.

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