list_themes

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it does so well. It explains that themes are computed deterministically (no LLM), that labels are trimmed medoids of real items, and that representative_item_id enables lookup. It also states the sort order. It does not mention potential side effects or permissions, but for a read-only list operation this is adequate.

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: the core purpose is front-loaded in the first sentence, followed by necessary algorithmic detail and a routing hint. Each sentence adds value, with no filler. The technical explanation is compact and relevant, and the pointer to get_theme is efficient.

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 existence of an output schema (which presumably documents the return format), the description does not need to detail response structure. It does explain the meaning of key fields (label, representative_item_id) and provides a lookup mechanism. It does not mention pagination or limit behavior, but with a single optional parameter, the tool likely returns all matching themes, so the definition 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 schema only defines `min_items` as an integer with a default, and schema description coverage is 0%. The description clarifies that `min_items` is a threshold for inclusion ('with at least `min_items` items'), adding meaningful semantics beyond the type definition. It does not discuss edge cases (e.g., negative values), but for a single parameter this is sufficient.

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 first sentence states a specific action (list feedback themes) with a clear condition (at least `min_items` items) and ordering (largest first). This is a precise verb+resource combination that distinguishes it from siblings like get_theme (single theme) and search_feedback (search), so an agent can immediately understand its scope.

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 explicitly directs users to `get_theme(theme_id)` when full detail on one theme is needed, which is a helpful alternative. However, it does not mention other siblings like search_feedback or severity_summary, nor does it state when list_themes is preferable to them. The primary use case is clear, but exclusion or comparison guidance is incomplete.

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