List Omarchy themes

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

No annotations are provided, so the description carries the burden. The verb 'List' clearly implies a read-only operation. However, it does not disclose return format, ordering, or potential error handling (e.g., if no themes exist). It provides minimal behavioral context beyond the action itself.

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?

A single, front-loaded sentence with zero filler. It immediately states what the tool does and nothing more. Perfectly concise for a zero-parameter list operation.

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 zero-parameter list tool with no output schema, the description is mostly sufficient. It does not clarify the nature of the returned items (e.g., names, identifiers, metadata), but given the simple scope, the basic description is adequate for an agent to call it. Slightly more detail on output would push it to a 5.

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?

Zero parameters exist, so the baseline is 4 according to calibration. The description correctly avoids redundant parameter details. No added value is needed for parameters.

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 ('all available Omarchy themes'). It clearly distinguishes itself from sibling tools like theme_current (which shows the current theme) and theme_set (which applies a theme). The phrase 'all available' clarifies breadth.

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?

Provides no guidance on when to use this tool versus alternatives like theme_current or theme_set. It does not mention that this tool is for discovering options while other tools handle inspection or application. No exclusions or context are given.

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