Manage Frontend Themes

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

The description discloses that action='set' only changes the backend-selected default, not user-specific choices, and that theme names are validated at call time. Annotations indicate destructiveHint=true and idempotentHint=true, which align with the described 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 well-structured with clear sections (When NOT to use, When to use, Caveats, Examples). It is concise, front-loaded with purpose, and every sentence contributes valuable information.

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?

Given the tool's moderate complexity (3 parameters, 100% schema coverage, output schema present, annotations provided), the description covers all necessary guidance: use cases, constraints, caveats, and examples. It is fully complete.

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?

All three parameters are fully described in the schema (100% coverage). The description adds context: mode defaults to light, theme_name can be 'default' or 'none', and examples illustrate usage. This provides meaning beyond the schema.

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 clearly states 'Manage Home Assistant frontend themes' and explains the two actions (list and set). It explicitly distinguishes from sibling tools like ha_manage_hacs and ha_config_set_yaml, making the purpose unambiguous.

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 includes explicit 'When NOT to use' and 'When to use' sections, stating that themes are YAML files not creatable via API and that community theme installation goes through HACS. It also provides examples for each action scenario.

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