list_themes

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds no extra behavioral details (e.g., pagination, sorting, or response format), but for a simple parameterless list operation this does not create a significant gap. The description neither contradicts annotations nor enriches them beyond the basic read-only nature.

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 sentence, using exactly the words needed to convey the purpose. There is no fluff or repetition, making it optimally concise and well-structured 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?

Given the tool's simplicity (no parameters, no output schema, basic list operation), the description is complete enough for an agent to understand the function. It does not specify the return format, but the practical nature of a theme list makes this self-evident, so minimal detail is acceptable.

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?

There are zero parameters, and schema coverage is trivially 100%. Per rubric, a baseline of 4 applies when no parameters exist; the description correctly adds no parameter explanations since there are none to describe.

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' and names the resource 'tweakcn themes', clearly indicating it enumerates available themes. It naturally distinguishes from sibling tools like get_theme, which retrieves a single theme, without needing explicit differentiation.

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?

No guidance is provided on when to use this tool versus alternatives such as get_theme or list_components. The description only states what it does, with no context on typical use cases, prerequisites, or exclusions. It is not misleading but lacks any usage direction.

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