Get Theme Mods (Kadence/Customizer)

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

Annotations already indicate read-only and non-destructive behavior. The description adds useful context beyond that, such as the dependency on the Ars Nova Bridge plugin and the return shape (active theme slug/name and theme_mods map). No behavioral surprises are hidden.

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-organized with an intro, dependency note, args list, and returns line. It is slightly verbose in repeating parameter details that are already in the schema, but every section serves a purpose and contributes to understanding.

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 tool with two parameters and no output schema, the description fully covers what the tool does, the necessary plugin dependency, and what to expect in the response. No critical information is missing.

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 for both parameters, including their optionality and defaults. The description repeats this information without adding any additional semantic nuance, so it meets the baseline for schema-covered parameters but does not exceed it.

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 provides a specific verb and resource ('Read the active theme's theme_mods') and elaborates with concrete examples (header layout, logo, colors, fonts). It clearly distinguishes itself from sibling tools like wp_get_settings and wp_get_sidebars by focusing on theme_mods and noting the companion plugin dependency.

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?

It clearly states when this tool is needed ('Core REST does not expose these') and gives a usage prerequisite (the Ars Nova Bridge plugin must be active). However, it does not explicitly name alternative tools or exclusion scenarios, so it falls short of a perfect 5.

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