list_themes

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

The description explains what a theme is (combination of dimension values) but does not disclose behavioral traits beyond the list action. No annotations exist, so more context about side effects, auth, or return characteristics would be beneficial.

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 two succinct sentences, each adding value without redundancy or unnecessary detail. It is front-loaded with the core action.

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 read-only list tool with no parameters, the description covers the purpose and explains the concept. It is adequate for an agent to understand when to use it, though it could slightly improve by explicitly stating it is safe.

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?

With no parameters, the description does not need to cover parameter semantics. It provides conceptual context (themes as combinations of dimension values), which is helpful. Baseline 4 is appropriate.

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 the verb 'list', resource 'themes', and scope 'all named themes defined in config', with an example. This distinguishes it from sibling tools like list_dimensions and resolve_theme.

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 does not provide explicit guidance on when to use this tool versus alternatives like list_dimensions or resolve_theme. It only describes the function without contextual usage advice.

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