loki_list_label_values

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

No annotations are provided, so the description carries the full burden. It does disclose that results are limited to a lookback window and that values are 'seen' in that window, which adds context. However, it omits any detail about pagination, limits, ordering, or behavior when the label has no values. This is adequate but not rich.

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 extremely concise: one purpose line followed by compact parameter documentation. Every sentence adds value, and the most important information is front-loaded. No filler or repetition.

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 low complexity (2 params, no nested objects) and the presence of an output schema, the description covers the essential invocation details. However, it lacks usage context, alternative-tool differentiation, and behavioral caveats, making it only moderately complete for agent decision-making.

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?

Schema coverage is 0%, but the description fully compensates by explaining both parameters. It gives concrete examples for label ('container', 'service_name', etc.) and lookback ('1h', '24h', '7d') with the default value. This is more informative than the bare schema properties.

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 operation: 'List all values seen for a given label in the lookback window.' It identifies the resource (label values) and the scope (lookback). It does not explicitly differentiate from sibling tools like loki_list_labels, but the wording is sufficiently specific to avoid major confusion.

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?

There is no guidance on when to use this tool versus alternatives such as loki_list_labels, loki_query_range, or loki_patterns. The description does not mention exclusions, prerequisites, or typical use cases beyond the literal action.

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