typora_list_themes

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

With no annotations, the description must disclose behavioral traits. It indicates the tool lists themes and highlights the active and dark theme, which is useful. However, it does not explicitly state that it is a read-only operation or describe any side effects, errors, or edge cases, relying on the implied nature of 'List'.

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, well-structured sentence that front-loads the action and resource. It conveys all necessary information without redundancy or filler.

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 there is no output schema, the description should clarify what the tool returns. It states it lists themes and indicates the active and dark theme, giving a reasonable expectation of output format. It does not mention potential empty results or format specifics, but for a simple list tool this is adequate.

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 tool has zero parameters, so the schema covers everything (100%). The baseline for 0 parameters is 4, and there is nothing for the description to add beyond what is already clear.

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 uses a specific verb ('List') with a clear resource ('all installed user themes and builtin themes') and adds distinguishing details (active theme and dark theme). This clearly separates it from sibling tools like typora_install_theme, typora_set_theme, and typora_get_theme_css, 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 implies usage for listing themes but does not explicitly state when to use this tool versus alternatives. There is no mention of alternatives or conditions for selection, leaving the agent to infer from the tool name and description alone.

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